Skip to main content

​
Overview

Binibit exposes its REST API across two hostnames:
GroupHostEndpoints
Market Datapublic-api.binibit.comPrimary public API — tickers, order book, trades, candles, currencies
Aggregator Compatibilityinternal-api.binibit.comSubset reshaped for CoinGecko / CoinMarketCap-style aggregator ingestion

​
Market Data (public-api.binibit.com)

MethodPathPage
GET/api/tickersTickers
GET/api/orderbookOrder Book
GET/api/dealsDeals
GET/api/ohlcOHLC
GET/api/currenciesCurrencies
GET/api/currencies/pairsCurrency Pairs
GET/api/currencies/commissionsCommissions
GET/api/healthcheckHealthcheck
The full OpenAPI 3.0 spec for public-api.binibit.com is published at /swagger/v1/swagger.json, with an interactive playground at /swagger/.

​
Aggregator Compatibility (internal-api.binibit.com)

MethodPathPage
GET/tickersTickers (aggregator)
GET/orderbookOrder Book (aggregator)
GET/historical_tradesHistorical Trades (aggregator)
GET/assetAsset (aggregator)
These endpoints follow the CoinGecko Integration API Standards v8 schema (Section A: Spot Exchanges) so aggregators (CoinGecko, CoinMarketCap, DefiLlama) can ingest Binibit market data without translation.

​
Authentication

The market data endpoints documented here are public — no API key required. See Authentication for the trading API.

​
Rate limits

See Rate Limits.

​
Conventions

  • All requests are GET with query parameters
  • All responses are JSON
  • All numeric values are decimals (prices, volumes) or integers (timestamps, IDs)
  • Timestamps differ between the two surfaces:
    • public-api.binibit.com uses ISO 8601 strings (2026-04-29T10:26:08.0053357Z) and seconds for ticker timestamp
    • internal-api.binibit.com aggregator namespace uses Unix milliseconds (CoinGecko convention)
  • Errors follow a unified envelope — see Errors

​
Try it

Every endpoint page below includes copy-paste curl examples that work against the live production API.

Start with /api/tickers

Single-pair ticker — the simplest call to confirm your integration works.