Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.whitebit.com/llms.txt

Use this file to discover all available pages before exploring further.

Fetch live market data from the WhiteBIT API in under 2 minutes. All Market Data endpoints are public — no account, no API key, no signing.

​
Prerequisites

  • A terminal or HTTP client (curl, Postman, or any programming language with HTTP support)
  • No WhiteBIT account needed
  • No API key needed
1

Check server availability

Confirm the API is reachable and operational.
curl https://whitebit.com/api/v4/public/ping
Expected response:
["pong"]
2

Fetch available markets

Retrieve the full list of trading pairs with minimum amounts and trading rules.
curl https://whitebit.com/api/v4/public/markets
Expected response (trimmed):
[
  {
    "name": "BTC_USDT",
    "stock": "BTC",
    "money": "USDT",
    "stockPrec": "6",
    "moneyPrec": "2",
    "makerFee": "0.001",
    "takerFee": "0.001",
    "minAmount": "0.0001",
    "minTotal": "1",
    "tradesEnabled": true,
    "type": "spot"
  },
  "..."
]
The response contains 900+ markets. Key fields: name (pair), stock (base currency), money (quote currency), minAmount (minimum order quantity), minTotal (minimum order value).For Go and PHP examples, see SDKs.
3

Get BTC_USDT ticker

Fetch 24-hour pricing and volume data. The ticker endpoint returns all pairs — filter for the desired market.
curl https://whitebit.com/api/v4/public/ticker
Expected response (BTC_USDT entry):
{
  "BTC_USDT": {
    "base_id": 1,
    "quote_id": 825,
    "last_price": "65432.10",
    "base_volume": "1234.567",
    "quote_volume": "80765432.10",
    "is_frozen": false,
    "change": "2.5"
  }
}
Key fields: last_price (most recent trade price), base_volume (24h volume in base currency), quote_volume (24h volume in quote currency), change (24h percentage change).
4

Fetch BTC_USDT orderbook

Retrieve the current orderbook depth. The limit parameter controls the number of price levels returned (1–100).
curl "https://whitebit.com/api/v4/public/orderbook/BTC_USDT?limit=5"
Expected response (trimmed):
{
  "ticker_id": "BTC_USDT",
  "timestamp": 1700000000,
  "asks": [
    ["65450.00", "0.500"],
    ["65460.00", "1.200"]
  ],
  "bids": [
    ["65430.00", "0.800"],
    ["65420.00", "1.500"]
  ]
}
Each entry is a [price, quantity] pair. asks = sell orders (ascending by price), bids = buy orders (descending by price).
5

Fetch recent trades

Retrieve the most recently executed trades for BTC_USDT.
curl https://whitebit.com/api/v4/public/trades/BTC_USDT
Expected response (trimmed):
[
  {
    "tradeID": 123456789,
    "price": "65435.50",
    "quote_volume": "0.015",
    "base_volume": "981.53",
    "trade_timestamp": 1700000000,
    "type": "buy"
  },
  "..."
]
Key fields: tradeID (unique identifier), price (execution price), type (“buy” or “sell”), trade_timestamp (Unix time in seconds).
These five public endpoints cover one-shot lookups. For continuous updates, switch to the WebSocket Quickstart — a single connection replaces every poll above.
No authentication — by design — Market Data endpoints are intentionally public. No API key, no HMAC signing, no account. WhiteBIT exposes pricing, orderbook, and trade data publicly to support price aggregators, data vendors, and integration testing without requiring account creation. Public endpoints have their own rate limits but no per-key restrictions.Polling vs streaming — The five steps above use REST (request → response). This is appropriate for one-time lookups but expensive for real-time monitoring: polling the ticker endpoint every second across hundreds of pairs exhausts rate limits quickly and adds latency. For continuous price or orderbook updates, use WebSocket instead — a single persistent connection streams updates as they occur, with no polling overhead.

​
What’s Next

Spot Trading Quickstart

Place a first trade — requires an API key with Trading permission.

WebSocket Quickstart

Stream real-time price updates instead of polling.

Authentication

Set up API keys and HMAC signing for authenticated endpoints.