How to check Binance API status and read error codes
Check the maintenance flag first, then probe the exact host and component; classify the HTTP response before handling Binance's numeric error code.
Configure any available plan and add-ons. Pay only for 48 hours.
Try proxiesTechnical guides, platform limitations, integration patterns, and practical proxy research.
Check the maintenance flag first, then probe the exact host and component; classify the HTTP response before handling Binance's numeric error code.
Binance.US runs on separate hosts, accounts, keys, limits, and product coverage; restricted requests to global endpoints can return HTTP 451 before authentication.
Binance rejects signed requests more than 1,000 ms ahead of its clock or older than recvWindow — 5,000 ms by default, 60,000 maximum.
Binance's matching engine runs in AWS Tokyo, so expect roughly 20–25 ms round trips from Tokyo and about 270 ms from Europe.
Binance allots 6,000 request weight per minute to each IP address on the Spot API; order limits are counted separately, per account.
The endpoint returns at most 1,000 candles per request, so pull long ranges in pages, advancing startTime past the last candle’s open time.
Binance expires spot trading on unrestricted keys after 90 days and blocks withdrawals entirely; whitelist your bot’s static egress IP once.