Skip to main content
POST
POST /support-chain returns data: true when Olympex supports a chain and data: false when it doesn’t. Use it to check one chain ID at runtime, for example a chain ID from your own configuration. To get every enabled chain at once, call GET /chains: both endpoints read the same list. Cache the result instead of calling it before every quote.

Send the chain ID as an integer

chainId is a JSON integer (137), as on every endpoint. A string such as "137" fails validation with 400 VALIDATION_ERROR and the detail "Invalid input: expected number, received string". Pass the IDs from GET /chains unchanged: they’re integers too. Conventions lists every chain ID field.
A chain ID that isn’t enabled returns 200 with data: false, not an error. Only an invalid body returns 400: invalid JSON, or a chainId that is missing or isn’t a positive integer. Other body fields are ignored.

Supported chains

A cross-chain transfer starts on a chain marked Yes in the cross-chain source column and ends on another chain in the table. Whether a specific pair has a route depends on the providers when you ask, so request a quote to confirm it. Limit orders and DCA execute only on the chains marked Yes in the last column, through the Olympex order contract on each one. Order signatures and allowances lists the contract address on each chain. GET /chains returns chain IDs only, without names, logos or capabilities. If your product needs them, keep this table’s names and columns in your code, and use GET /chains to decide which of these chains to offer: offer a chain only while its ID is in the response. POST /support-chain checks one chain ID against the same list. GET /tokens lists the tokens on each chain. Supported chains covers token addresses, amounts and decimals.

Authorizations

x-api-key-id
string
header
required

Your API key ID (UUID). See Sign requests.

x-value-info
string
header
required

Base64 of timestamp + "\n" + nonce + "\n" + bodyHash, where timestamp is Unix seconds, nonce is 24 new hexadecimal characters and bodyHash is the unpadded base64url SHA-256 of the canonical body.

x-passphrase
string
header
required

Your account passphrase. Treat it like the secret key.

x-signature
string
header
required

Lowercase hex HMAC-SHA256 (signature v2), keyed with your secret key string (UTF-8, not decoded), of seven lines joined with \n, with no trailing newline: OLPX-HMAC-SHA256-V2, timestamp, nonce, the uppercase method, path, canonicalQuery and bodyHash. path is the request path including /api/v1, without the query string, for example /api/v1/limit-order/<id>. canonicalQuery is the query parameters decoded (+ is a space), sorted by key and then by value, re-encoded per RFC 3986 and joined with &, or the empty string when there is no query. Headers signed for one request are rejected on any other. See Sign requests.

Body

application/json
chainId
integer
required

EVM chain ID as an integer, for example 137.

Required range: 0 < x <= 9007199254740991
Example:

137

Response

Chain support status.

success
enum<boolean>
required
Available options:
true
data
boolean
required

true when the chain is supported.

meta
object
required