Skip to main content

Documentation Index

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

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

Not for market data. All endpoints under public-api.binibit.com/api/* (tickers, orderbook, deals, ohlc, currencies, healthcheck) and the aggregator-spec namespace are public.The trading API on public-api.binibit.com (create/cancel orders, withdrawals) does require HMAC-SHA256 request signing with an API key + secret — see the v2 roadmap.
public-api.binibit.com is the primary REST API. internal-api.binibit.com/.../getcoingecko/* is a small subset of market data reshaped to match the CoinGecko Integration API Standards v8 — kept around so data aggregators can ingest without translation. See Base URL.
Tickers and order books refresh every few seconds. Cache for at least 5 seconds on your side; polling more frequently will not return fresher data and will count against your rate limit.
Pairs with zero 24-hour volume or empty order books are excluded from the aggregator-spec /tickers. They still appear in the primary API’s /api/currencies/pairs.
Numbers. JavaScript’s native Number type is precise for the prices and volumes seen on this exchange, but for safety use a high-precision decimal library (decimal.js, bignumber.js, Python Decimal, Go big.Float) when doing arithmetic.
price = X means the most recent trade for the pair was at X units of the target currency per one unit of the base currency. For AAVE_USDT with price = 97.44, one AAVE last traded for 97.44 USDT.
Historical naming. The aggregator-spec namespace will get a cleaner alias (/v1/spot/market/*) in a future release; the legacy host will continue to work as a redirect for at least 90 days after migration.
Not yet. WebSocket streams for tickers, order book, and trades are on the v2 roadmap. Watch the GitHub repo for release notifications.
Yes. Attribution is appreciated but not required for non-commercial use. For high-volume commercial use, contact api@binibit.com for elevated rate limits.
Yes. The primary API publishes an OpenAPI 3.0 spec at https://public-api.binibit.com/swagger/v1/swagger.json, with an interactive playground at /swagger/.
The type field reflects the taker side:
  • buy — taker bought (an ask was removed from the order book)
  • sell — taker sold (a bid was removed from the order book)
Each trade has exactly one taker, so each trade appears in exactly one of the two arrays.
On the aggregator-spec namespace they are milliseconds since the Unix epoch, e.g. 17773973154662026-04-28T22:37:55.466Z. The primary API uses ISO 8601 strings instead. See Timestamps.
Email api@binibit.com. We can:
  • Whitelist your IP for unlimited rate limit
  • Provide direct contact for the data engineering team
  • Coordinate on listing review and verification

Didn’t find your answer?

Contact support

Reach out to the Binibit API team.