Skip to main content
GET
GET /chains returns the IDs of the chains Olympex has enabled, as integers in ascending order. It is the source of truth for which chains to offer: call it instead of hard-coding which chains are enabled. It returns IDs only: take names and capabilities from Supported chains. Then get each chain’s tokens with GET /tokens. POST /support-chain checks a single chain against the same list.

Chain IDs are integers

data.chainIds holds integers (137), the type every endpoint takes: pass them unchanged to GET /tokens, POST /quotes, POST /swap, POST /support-chain, POST /tx-status, GET /transactions/{hash}, limit orders and DCA. Conventions lists every chain ID field.

Cache the list

Call GET /chains when your service starts and refresh it on the same schedule as your token lists, instead of before every request. When a chain leaves the list, stop offering it. Supported chains shows the chains enabled today and what each one supports. An enabled chain doesn’t mean every pair has a route: request a quote to confirm a pair. Limit orders and DCA execute only on the chains listed in The order contract.

Sign the empty string

GET /chains has no body, so you sign the empty string: its bodyHash is 47DEQpj8HBSa-_TImW-5JCeuQeRkm5NMpJWZG3hSuFU. The method and the path, /api/v1/chains, are signed with it.

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.

Response

Enabled chain IDs.

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