GET /api/v1/bridge/assets

List bridgeable chains and assets

List bridgeable chains and assets.

operationId: getBridgeAssets

Declared server differs from the callable one. This path declares its own servers base of https://exchange.nexus.xyz, without the /api/exchange mount the document default carries. Measured 2026-09-02, the override is not routed — https://exchange.nexus.xyz/api/v1/bridge/assets returns 404 while the gateway form in the sample below is routed. A client generated from this contract will aim at the override; pin the gateway base until the per-network hosts are live. See Networks.

Not reachable through CCXT. Nexus-specific asset bridging. CCXT's deposit/withdraw methods model a venue's own custody, not a cross-chain bridge, and mapping them would misdescribe both.

Authentication: hmacAuth.

Returns the supported chains and, per chain, the depositable assets (USDC, USDX) with their decimals, minimum amount and required confirmations, and the withdrawable assets (USDX) with their minimum amount and flat fee. Metadata only — it moves no funds and reads no account state, but carries the standard /v1/bridge HMAC auth like the rest of the surface.

Asset scope is USDC and USDX; USDT is out of scope for this cut. chain_id is the serving network's numbered chain (1 on mainnet, 11155111/Sepolia on testnet) and is null on a local instance that serves no numbered chain. Arbitrum becomes another chains[] entry later with no shape change.

The published min_amount is provisional: the delivered-amount minimum is still being reconciled against the provider's quoted limits (ENG-8297), because a fixed-input funding route can deliver net of fees below a quote-time minimum. Treat it as a floor that may rise, not a settled figure.

Responses

Status	Body	Meaning
200	BridgeAssetsResponse	Supported bridge chains and their deposit/withdraw assets.
401	— (no schema declared)	—
429	— (no schema declared)	—

Example

cURL

curl -X GET 'https://exchange.nexus.xyz/api/exchange/api/v1/bridge/assets' \
  -H 'X-API-Key: nx_7f3a1b...' \
  -H 'X-Timestamp: 1776033911836' \
  -H 'X-Signature: <hmac-sha256>'

Python

import requests

headers = {
    "X-API-Key": "nx_7f3a1b...",
    "X-Timestamp": "1776033911836",
    "X-Signature": "<hmac-sha256>"
}

response = requests.get("https://exchange.nexus.xyz/api/exchange/api/v1/bridge/assets", headers=headers)
response.raise_for_status()
print(response.json())

TypeScript

const response = await fetch("https://exchange.nexus.xyz/api/exchange/api/v1/bridge/assets", {
  method: "GET",
  headers: {
    "X-API-Key": "nx_7f3a1b...",
    "X-Timestamp": "1776033911836",
    "X-Signature": "<hmac-sha256>"
  },
});
if (!response.ok) throw new Error(`${response.status} ${await response.text()}`);
console.log(await response.json());

X-Signature is a placeholder: it is derived from this specific request. See Authentication for the canonical string and the HMAC rule.

---

_{Generated from eng/apps/exchange/api/openapi.json (spec 0.9.36). Do not edit by hand — regenerate with python3 product/docs/tools/api-reference/generate.py. Hand-authored context lives in the Guides pages.}