Changelog
2026-04-29
- Signature documentation corrected: the
PreHashformula is now stated explicitly astimestamp + method + requestPath + (?queryString)? + body, andrequestPathexcludes the gateway prefixes/spot/openand/futures/open— sign with/sapi/v1/...or/fapi/v1/...only. The most common integration failures are documented in the FAQ checklist. - Spot
/sapiand futures/fapirewritten to match the actual backend controllers (Spot trading, Futures trading). Added or corrected several fields (symbols.limitPriceMin/limitVolumeMin/marketBuyMin/marketSellMin, futures klineintervalaccepts1h,myTrades.limitis capped at 100, etc.). - Added futures endpoints:
all_ticker,get_all_indexPrice,public_all_index_tag_price,openOrdersCount,tradesRecord,adlRecord,liquidationList,profitLossOrder,trigger_order_list,cancel_trigger_order,positions,capital,edit_lever,edit_user_position_model. - Added documentation for the RSA-signed funds-transfer endpoints
futures_transfer/futures_balance(these do not reuseX-CH-SIGN). - Added end-to-end signing examples for both GET and POST in General information (PreHash + openssl + curl).
2026-03-16
- New release online
To optimize system architecture and improve service stability, the platform will migrate the Open API routing domain. The legacy Open API domain api.bitbaby.com will move to openapi.bitbaby.com. All Open API users should update endpoint hostnames as soon as possible.
Important: This migration only changes the subdomain; existing API paths stay the same, for example:
- Before:
https://api.bitbaby.com/spot/open/ - After:
https://openapi.bitbaby.com/spot/open/
Paths, parameters, and calling conventions remain unchanged.
Migration schedule:
- New Open API hostname:
openapi.bitbaby.com - Legacy domain sunset: March 20, 2026, 18:00 (UTC+8)
After this time, Open API routes under api.bitbaby.com will stop serving. If you do not migrate in time, API calls may fail or orders may not be placed.