Supported Networks

Query the API for networks in the environment you are calling. Do not assume a fixed list of chain identifiers.

Environment behaviour

Environment	Networks returned
Test	Test networks
Live	Mainnet networks

See Sandbox vs production for hosts and key prefixes.

List networks

GET /v1/networks

Auth: pk_* or sk_*.

{
  "status": true,
  "message": "Networks retrieved successfully",
  "data": [
    {
      "id": 1,
      "identifier": "BSC",
      "logo": "https://…",
      "chain_id": 56,
      "chain_id_hex": "0x38",
      "explorer_url": "https://bscscan.com",
      "is_testnet": false,
      "is_evm": true
    }
  ]
}

Field	Use in integration
`identifier`	Pass as `network` on crypto order legs
`chain_id` / `chain_id_hex`	Wallet context for EVM chains
`is_evm`	Whether the network uses EVM address formats
`explorer_url`	Link users to on-chain transaction status
`is_testnet`	Confirms sandbox vs production alignment

Single network

GET /v1/networks/:identifier

:identifier matches the identifier field (for example BSC).

Endpoint	Purpose
`GET /v1/networks/:identifier/crypto-currencies`	Tokens on this chain
`GET /v1/crypto-currencies/:identifier/networks`	Networks where a currency is available

A mainnet identifier from production will not resolve in sandbox. Always load network pickers from GET /v1/networks in the target environment.

Supported assets

Crypto symbols for order legs.

Swap quickstart

Same-network crypto-to-crypto orders.

Introduction

Getting Started

Quickstarts

Liquidity Providers

Resources

Environment behaviour

List networks

Single network

Supported assets

Swap quickstart

​Environment behaviour

​List networks

​Single network

​Related endpoints

Supported assets

Swap quickstart

Environment behaviour

List networks

Single network

Related endpoints