Support

​

Contact

​

Before you write

• An error envelope. Look up error.code and the HTTP status in Errors and retries. For 400 VALIDATION_ERROR, error.details names each field at fault.
• 401 or 403 on a signed request. Work through the signing troubleshooting table, and test your implementation against the known-answer vectors on the same page. If correctly signed requests keep failing, email partners@olympex.io.
• 404 NOT_FOUND with "No route for …". No endpoint matches the method and path. Check that the URL starts with the base URL, that the method is the one the endpoint page shows, and that the path is lowercase, for example /support-chain.
• 404 NOT_FOUND for an order or strategy ID, with a message that names the resource. No limit order, DCA strategy or DCA order with that ID belongs to the API key you signed with: the ID doesn’t exist, or another API key created it. See Not found.
• 409 CONFLICT on a limit order. The order is no longer pending, so it can’t be changed or cancelled. Read it with GET /limit-order/{id} and check its status.
• A limit order or DCA order that doesn’t execute or fails. Read reasonFail[] on the limit order or errorMessage on the DCA order. Check that the maker still holds the tokens, that its allowance to the order contract covers the order (plus the execution gas, for a limit order), and that the order signature recovers to the maker. For a limit order, also check that tokenASymbol and tokenBSymbol match your tokens.
• “The browser blocked the response” in the API console. Click Copy as cURL and run the request from a terminal. Add -i to the command (or -D -) to see the status and the apigw-requestid header. See API console.
• A swap whose eth_estimateGas reverts. Check the allowance, the balance and the expiry, then build the swap again with the next source in the quote’s aggregatorOrder, or request a new quote. See Falling back with aggregatorOrder.
• 422 NO_ROUTE, or a chain or token pair without a route. Retry later with backoff: sources can be briefly unavailable. If it persists, check Supported chains and tokens, then request a quote for another amount or pair.
• A suspected outage. Olympex doesn’t publish a status page. If 500 or 503 responses persist across endpoints after retries with backoff, email partners@olympex.io with the request IDs and UTC times of a few failures.

​

What to include

Subject: POST /quotes returns 422 NO_ROUTE for USDT to 0x000000000000000000000000000000000000dEaD on Polygon

meta.requestId: E7ef-j_MoAMEPBw=
Endpoint and status: POST /quotes, 422
Time (UTC): 2026-10-08T14:38:04Z
API key ID: 00000000-0000-4000-8000-000000000000

Request body:
{"mode":"single-chain","params":{"amount":"10","chainId":137,"gasPrice":"35","inTokenAddress":"0xc2132d05d31c914a87c6611c10748aeb04b58e8f","outTokenAddress":"0x000000000000000000000000000000000000dEaD","slippage":"1"}}

Response body:
{"success":false,"error":{"code":"NO_ROUTE","message":"No route found for this pair and amount. Providers may also be temporarily unavailable; retrying later can succeed.","details":[{"message":"The quote could be retrieved but the route is not available"}]},"meta":{"requestId":"E7ef-j_MoAMEPBw=","version":"v1","accountType":"integrator","apiKeyId":"00000000-0000-4000-8000-000000000000"}}

Expected: a route for this pair.
Observed: 422 NO_ROUTE on every attempt since 14:30 UTC. Other pairs on Polygon work.

​

Report a leaked credential

1. Email partners@olympex.io and ask to deactivate the account. Include the API key ID only.
2. If the account has open limit orders or DCA strategies, set each maker’s allowance to the order contract to 0. Anyone with the credentials can create and change orders, and the allowance is what limits them. See Stop everything.
3. Create a new API account and move your integration to its credentials.
4. Remove the exposed values from wherever they leaked: logs, tickets, chats or repository history.

​

Report a security issue

​

Related