network in a response is one of these canonical keys.
All four networks are served by
https://api.multiliquid.xyz. Moving an integration from a test network to production changes only the network key, not the host or the API key.
A GET or DELETE route takes network in its query string, and a POST or PUT route takes it in its JSON body. A body that sends back a prepared object names it inside that object, as order.network, cancellation.network, or redemption.network.
Networks by route
GET /v1/networks lists every network with its runtime, chain ID or Solana cluster, block explorer, and whether the API serves it, as Discovery describes. GET /v1/networks, GET /v1/organization, and GET /v1/submissions/{submissionId} take no network: the submission ID identifies its network.
Rejected keys
An unknown or unsupported network is rejected with an error whose message names the value as sent and the route’s canonical keys, and whosedetails.field names it: network, or order.network, cancellation.network, or redemption.network where a body sends back a prepared object. An older network name, mainnet, sepolia, solana, or solana-devnet, is also followed by its canonical key in parentheses. On the redemption routes, network=mainnet is rejected with:
400 with code INVALID_REQUEST when the key is in the query string, and 422 with code INVALID_BODY when it is in a JSON body.
For example, redemptions serve only Ethereum mainnet, so this request is rejected with 400, and the message lists evm-mainnet as the only supported network:
cp:operate scope, a POST /v1/batch-orders/nonce-accounts whose body names evm-mainnet is rejected with 422 and code INVALID_BODY; the message names evm-mainnet and lists svm-mainnet and svm-devnet as the supported networks.
The message wording can change. Errors describes the full error body and how to handle it.
Deployment info
GET /v1/info, GET /v1/info/evm, and GET /v1/info/svm take an optional network. With it, the route returns the selected deployment directly. Without it, GET /v1/info returns every deployment keyed by runtime (evm, svm) and then chain, and GET /v1/info/evm and GET /v1/info/svm return their runtime’s deployments keyed by chain.
runtime (evm or svm) on /v1/info, and chain on the runtime routes (mainnet or sepolia on /v1/info/evm, mainnet or devnet on /v1/info/svm). Supplying network together with either is a 400, and so is an unsupported runtime or chain, whose details.field names the parameter.
On these routes, network is matched case-insensitively and also accepts each older network name and chain value that names exactly one network on that route:
mainnet is rejected with 400 on /v1/info/svm and /v1/info because it could mean evm-mainnet or svm-mainnet. The error suggests only the keys that route serves: svm-mainnet on /v1/info/svm, and evm-mainnet or svm-mainnet on /v1/info.
Related
API introduction
Base URL, test networks, authentication, and the interactive reference.
Errors
The error envelope and every error code.