1
Verify the keys
Verify your keys by ensuring the headers are correctly set for all the
authenticated requests and check in the GlueX portal that your key is
active and has not been revoked or rotated
2
Confirm Endpoints
Ensure you are targeting the correct environment by verifying the base URL.
Production endpoints are
https://router.gluex.xyz
for quotes and
https://exchange-rates.gluex.xyz
for exchange rates3
Validate Request Payload
Confirm the payload matches the schema ensuring all required fields are set
and all the data matches the expected types
4
Inspect HTTP Status Codes
Examine the HTTP status code returned by the API. A
400
indicates a
malformed request, 401
/403
indicate authentication or authorization
failure, 429
signals rate limiting and any 5xx
indicates a server side
error5
Review Rate Limits
Verify that you are within your allowed request rate to avoid throttling. If
you receive
429
responses, implement exponential backoff and reduce request
frequency6
Confirm Token Addresses and Chains
Make sure the token contract addresses exist on the specified chain and are
correctly checksummed
7
Enable Debug Logging
Turn on verbose logging in your client or SDK to capture full request and
response details, including headers and bodies. Look for hidden error messages
or stack traces in the logs