Pairs

Enumerate trading pairs. Pair naming ({to}{from}) and availability semantics are explained in Rates & Pricing.

List Pairs

GET /pair/

Request

curl -X GET "https://api.n.exchange/en/api/v2/pair/" \
  -H "Accept: application/json" \
  -H "Authorization: ApiKey YOUR_API_KEY"

Authentication: API key required — see Authentication.

Parameters: none. The response is a plain array (no pagination).

Response

Field	Type	Description
name	string	Pair name, {to}{from} — e.g. BTCUSDC = send USDC, receive BTC
to	string	Currency you receive
from	string	Currency you send
disabled	boolean	Whether the pair is currently disabled (computed dynamically)

Example response:

[
  {
    "name": "BTCUSDC",
    "to": "BTC",
    "from": "USDC",
    "disabled": false
  },
  {
    "name": "ETHBTC",
    "to": "ETH",
    "from": "BTC",
    "disabled": false
  }
]

Use /rate/ for tradability

GET /pair/ lists every configured pair; disabled: false does not guarantee live liquidity right now, and availability can differ per direction. The set of pairs actually quotable at this moment is whatever GET /rate/ returns for your filters.

Get Pair Details

GET /pair/{name}/

Path parameters:

Parameter	Type	Required	Description
name	string	Yes	Pair name (e.g. BTCUSDC), or a special value below

Special values:

• random — a random active pair (user-specific when authenticated)
• most_traded — the most traded pair

curl -X GET "https://api.n.exchange/en/api/v2/pair/BTCUSDC/" \
  -H "Accept: application/json" \
  -H "Authorization: ApiKey YOUR_API_KEY"

{
  "name": "BTCUSDC",
  "to": "BTC",
  "from": "USDC",
  "disabled": false
}

Errors

Status	Meaning	Body
401	Missing/invalid API key	{"detail": "Authentication credentials were not provided."}
404	Unknown pair name	{"detail": "Not found"}
417	random failed to find an active pair after several attempts	{"detail": "Exceeded random pair getting attempts."}

Next steps

• Rates — live pricing per pair
• Rates & Pricing concepts — availability semantics