mirror of
https://github.com/discountry/ritmex-bot.git
synced 2026-09-09 16:28:06 +00:00
DisneyandGitHub
d6399b92aa
* add docs * Add Binance exchange support - Updated the environment configuration to include Binance as a selectable exchange option. - Enhanced the README documentation to reflect the addition of Binance. - Implemented the Binance exchange adapter and integrated it into the existing exchange framework. - Modified the basis arbitrage strategy to support Binance alongside existing exchanges. - Added tests to ensure proper functionality and integration of Binance within the trading system. * Enhance README with detailed Binance exchange configuration - Added comprehensive instructions for setting up Binance as an exchange option. - Included environment variable specifications for API keys, market types, and trading symbols. - Provided examples for both perpetual and spot trading strategies. - Clarified the use of WebSocket and REST for the Binance adapter. * Enhance exchange support and testing framework - Added a new test suite for exchange contracts to ensure consistency and functionality across supported exchanges. - Refactored exchange ID handling to utilize a centralized list of supported exchanges, improving maintainability. - Updated CLI argument parsing and help documentation to reflect the new exchange structure. - Introduced utility functions for validating supported exchanges and their display names. - Enhanced the BasisApp and strategy runner to leverage the new exchange validation logic. - Added a new test command for running exchange-related tests. * Refactor exchange contract tests and update CLI commands - Removed the trailing supported exchanges set and simplified the logic for trailing stop support in the exchange contract tests. - Updated the test command for exchange contracts to exclude unnecessary tests, streamlining the testing process. - Enhanced test descriptions for clarity and improved understanding of the functionality being tested.
40 lines
3.2 KiB
Markdown
40 lines
3.2 KiB
Markdown
---
|
||
title: "LIMITS | Binance Open Platform"
|
||
source: "https://developers.binance.com/docs/binance-spot-api-docs/testnet/rest-api/limits"
|
||
fetched_at: "2026-02-26T10:38:10.693Z"
|
||
---
|
||
### General Info on Limits[](https://developers.binance.com/docs/binance-spot-api-docs/testnet/rest-api/limits)
|
||
|
||
- The following `intervalLetter` values for headers:
|
||
- SECOND => S
|
||
- MINUTE => M
|
||
- HOUR => H
|
||
- DAY => D
|
||
- `intervalNum` describes the amount of the interval. For example, `intervalNum` 5 with `intervalLetter` M means "Every 5 minutes".
|
||
- The `/api/v3/exchangeInfo` `rateLimits` array contains objects related to the exchange's `RAW_REQUESTS`, `REQUEST_WEIGHT`, and `ORDERS` rate limits. These are further defined in the `ENUM definitions` section under `Rate limiters (rateLimitType)`.
|
||
- Requests fail with HTTP status code 429 when you exceed the request rate limit.
|
||
|
||
### IP Limits[](https://developers.binance.com/docs/binance-spot-api-docs/testnet/rest-api/limits)
|
||
|
||
- Every request will contain `X-MBX-USED-WEIGHT-(intervalNum)(intervalLetter)` in the response headers which has the current used weight for the IP for all request rate limiters defined.
|
||
- Each route has a `weight` which determines for the number of requests each endpoint counts for. Heavier endpoints and endpoints that do operations on multiple symbols will have a heavier `weight`.
|
||
- When a 429 is received, it's your obligation as an API to back off and not spam the API.
|
||
- **Repeatedly violating rate limits and/or failing to back off after receiving 429s will result in an automated IP ban (HTTP status 418).**
|
||
- IP bans are tracked and **scale in duration** for repeat offenders, **from 2 minutes to 3 days**.
|
||
- A `Retry-After` header is sent with a 418 or 429 responses and will give the **number of seconds** required to wait, in the case of a 429, to prevent a ban, or, in the case of a 418, until the ban is over.
|
||
- **The limits on the API are based on the IPs, not the API keys.**
|
||
|
||
### Unfilled Order Count[](https://developers.binance.com/docs/binance-spot-api-docs/testnet/rest-api/limits)
|
||
|
||
- Every successful order response will contain a `X-MBX-ORDER-COUNT-(intervalNum)(intervalLetter)` header indicating how many orders you have placed for that interval.
|
||
|
||
To monitor this, refer to [`GET api/v3/rateLimit/order`](https://developers.binance.com/docs/binance-spot-api-docs/testnet/rest-api/account-endpoints).
|
||
- Rejected/unsuccessful orders are not guaranteed to have `X-MBX-ORDER-COUNT-**` headers in the response.
|
||
- If you have exceeded this, you will receive a 429 error with the `Retry-After` header.
|
||
- **Please note that if your orders are consistently filled by trades, you can continuously place orders on the API**. For more information, please see [Spot Unfilled Order Count Rules](https://developers.binance.com/docs/binance-spot-api-docs/faqs/order_count_decrement).
|
||
- **The number of unfilled orders is tracked for each account.**
|
||
|
||
- [General Info on Limits](https://developers.binance.com/docs/binance-spot-api-docs/testnet/rest-api/limits)
|
||
- [IP Limits](https://developers.binance.com/docs/binance-spot-api-docs/testnet/rest-api/limits)
|
||
- [Unfilled Order Count](https://developers.binance.com/docs/binance-spot-api-docs/testnet/rest-api/limits)
|