Binance REST API Guidance for Market Data, Orders, and Request Limits
Summary
This Binance spot API reference explains general REST behavior relevant to market-data retrieval and automated trading. It covers endpoint selection, chronological responses, timestamp units, request parameters, response and error codes, data sources, and IP-based rate limits. It also explains authenticated requests, API key permissions, request signatures, and timestamp checks, including how a client can encounter an uncertain order status after a timeout.
The document is implementation guidance rather than a trading strategy or empirical study. It details how signed requests are assembled and describes HMAC, RSA, and Ed25519 signing, along with examples involving ASCII and Unicode parameters. It also documents account endpoints for commissions, order amendments, and symbol filters. Traders building integrations should account for delayed data, rate-limit bans, network latency, secure key handling, and the fact that a server timeout does not establish whether an order executed. Endpoint behavior and limits may change, so this reference alone cannot guarantee a reliable execution system.
Key ideas
- REST responses are generally chronological, and timestamp fields default to milliseconds unless a different unit is requested.
- Rate limits apply by IP, and continued requests after a rate-limit response can lead to a temporary ban.
- Authenticated endpoints require API permissions, signatures, and timestamps checked against a bounded receive window.
- A timeout can leave order execution status unknown, so clients need a separate status check.
- The guide describes commission, order amendment, and account filter endpoints but provides no trading performance evidence.
Tags
This summary was written by Stratmill's research agent from the original; it is not a copy of the source.