List Markets

The pair list a client builds its trading screen from: which markets are tradable, how to format the numbers on each, and what a fill costs.

GET/api/marketsAuth: Required

Query Parameters

pagenumber

Page number. Default 1.

per_pagenumber

Items per page. Default 20, maximum 1000.

Response

A paginated envelope; the markets are in items.

total_countnumberRequired

Total number of markets across all pages.

itemsarrayRequired

The markets.

More attributes

GET/api/markets

curl -G 'https://api.example.com/api/markets' \
  -H 'Api-Token: YOUR_API_TOKEN' \
  --data-urlencode 'page=1' \
  --data-urlencode 'per_page=20'

EXAMPLE RESPONSE

{
  "total_count": 17,
  "per_page": 1,
  "total_pages": 17,
  "page": 1,
  "prev_page": null,
  "next_page": 2,
  "items": [
    {
      "market": "xrpusdt",
      "active": true,
      "bid_asset_id": "usdt",
      "ask_asset_id": "xrp",
      "base_precision": 0,
      "quote_precision": 5,
      "price_precision": 4,
      "maker_fee": "0.001",
      "taker_fee": "0.001",
      "created_at": "2020-08-04T17:20:36.000Z",
      "updated_at": "2026-07-27T12:40:37.000Z"
    }
  ]
}

bid is the quote asset, ask is the base asset

This is the opposite of what the names suggest to most readers, and it is easy to get backwards because bid and base start with the same letter.

On xrpusdt:

Field	Value	Which side
ask_asset_id	xrp	base — what is traded
bid_asset_id	usdt	quote — what it is priced in

The precision fields use the other naming, so pair them carefully: base_precision applies to the asset in ask_asset_id, and quote_precision applies to the asset in bid_asset_id.

Reading these two fields the wrong way round inverts every pair on a trading screen, so it is worth asserting once in your integration tests.

Minimum order size is not in this response

A market's minimum order size is enforced when an order is placed rather than published here, so handle that refusal in your order flow. See Trading.