GraphQL
credentials let Galxe fetch data from your authorized GraphQL endpoint, including Subgraph
endpoints. During user verification, Galxe sends a query with the user’s address to the endpoint. The response is evaluated by a JavaScript(ES6)
expression, returning 1
(eligible) or 0
(not eligible).
GraphQL API
and waits for the response.
response.body
from your backend using predefined expressions to determine if the user meets the conditions.
35.185.209.0
and 35.203.155.18
are our outbound IPs. Failure to whitelist these may result in 403 errors when accessing the service.GraphQL
endpoint.Key-value
pairs included in the GraphQL
request.
{}
of the pre-filled template, for example:
$address
: Replaced with the user’s wallet address as a hexadecimal string with the 0x
prefix, e.g., 0x95ad73...
.
$socialId
: Used when user information is not an address (email or Telegram ID) and replaced with the respective information.
0x
), Galxe converts them to lowercase before sending to your endpoint.GraphQL
is in JSON
format by default, compliant with Galxe’s standards.
JavaScript (ES6)
function with the type signature (object) => int
.
resp
as a parameter.
1
or 0
, indicating whether the address qualifies for the credential.
true/false
) or strings ("0"/"1"
).anonymous
, with the first line written in the following format:
GraphQL
, you can achieve secure access through request headers (such as API KEY
or tokens
). This information will not be exposed by Galxe, and only users with Space admin privileges can view it.
OPTIONS
requests during API configuration to validate the API’s correctness.