> ## Documentation Index
> Fetch the complete documentation index at: https://docs.multiliquid.xyz/llms.txt
> Use this file to discover all available pages before exploring further.

# Network keys

> How the API names networks, and which networks each route serves.

Every route names a network by its runtime-prefixed key, and every `network` in a response is one of these canonical keys.

| Network key | Runtime | Network | Purpose |
| - | - | - | - |
| `evm-mainnet` | EVM | Ethereum mainnet | Production |
| `evm-sepolia` | EVM | Ethereum Sepolia | Testing |
| `svm-mainnet` | SVM | Solana mainnet-beta | Production |
| `svm-devnet` | SVM | Solana devnet | Testing |

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

| Routes | Networks |
| - | - |
| Discovery: `GET /v1/swap/pairs` | All four |
| Swap: `GET /v1/swap/quote`, `POST /v1/swap/build`, `POST /v1/swap/decode` | All four |
| Submissions: `POST /v1/submissions`, `GET /v1/submissions` | All four |
| Transaction history and volume: `GET /v1/transactions`, `GET /v1/volume` | `evm-mainnet`, `evm-sepolia` |
| Redemptions: every `/v1/redemptions` route, including `prepare` | `evm-mainnet` only, which is the default when `network` is omitted |
| Batch orders: `/v1/batch-orders` routes | All four; `POST /v1/batch-orders/nonce-accounts` accepts only `svm-mainnet` and `svm-devnet` |
| Organization delegates: `GET /v1/organizations/{organizationId}/delegates` | `evm-mainnet`, `evm-sepolia` |
| Delegate administration: `GET /v1/organizations/{organizationId}/delegates/{delegateId}/admin/state`, `POST /v1/organizations/{organizationId}/delegates/{delegateId}/admin/prepare` | `evm-mainnet`, `evm-sepolia` |
| Deployment info: `GET /v1/info`, `GET /v1/info/evm`, `GET /v1/info/svm` | Optional, as [Deployment info](#deployment-info) describes |

`GET /v1/networks` lists every network with its runtime, chain ID or Solana cluster, block explorer, and whether the API serves it, as [Discovery](https://docs.multiliquid.xyz/api-reference/swap/discovery.md#networks) 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 whose `details.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:

```text theme={null}
invalid value for query parameter `network`: unsupported network `mainnet` (evm-mainnet); supported networks: evm-mainnet
```

The status is `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:

```bash theme={null}
curl "https://api.multiliquid.xyz/v1/redemptions?user=0x2222222222222222222222222222222222222222&network=evm-sepolia"
```

Likewise, the Solana-only batch order route rejects an Ethereum network. With a credential that has the `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](https://docs.multiliquid.xyz/api-reference/guides/errors.md) 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.

```bash theme={null}
curl "https://api.multiliquid.xyz/v1/info/evm?network=evm-mainnet"
```

The older filters still work but are deprecated: `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:

| Route | Older names accepted in `network` | `chain` values accepted in `network` | Rejected as ambiguous |
| - | - | - | - |
| `/v1/info/evm` | `mainnet`, `sepolia` | `mainnet`, `sepolia` (the same names) | None |
| `/v1/info/svm` | `solana`, `solana-devnet` | `devnet` | `mainnet` |
| `/v1/info` | `sepolia`, `solana`, `solana-devnet` | `devnet` | `mainnet` |

`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

> [card] [API introduction](https://docs.multiliquid.xyz/api-reference/introduction.md)
>
> Base URL, test networks, authentication, and the interactive reference.

> [card] [Errors](https://docs.multiliquid.xyz/api-reference/guides/errors.md)
>
> The error envelope and every error code.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.