Issue with sequential execution of /updateAds on Binance C2C API

Currently, I need to update 20 ads using the /updateAds endpoint of the Binance C2C API. To avoid the “Too many requests” error, it is critical that calls to this endpoint are made sequentially, i.e. one after the other, rather than concurrently.

Requirements:

Sequential calls: Each request to /updateAds must be executed only after the previous one has finished.
5-second interval: An interval of at least 5 seconds must be respected between each call to comply with API limitations and avoid crashes.
Stability: The process must be stable and not generate errors due to excessive requests in a short period of time.
Current issue:

When I try to update ads, if the requests are not completely sequential, the API returns the “Too many requests” error.
I need to make sure that each request completes before sending the next one and that the 5-second interval is respected correctly.
I appreciate your support in finding a solution or best practices to handle this scenario without violating API limitations.

Regards,

Hey,
As this endpoint is not public, I would suggest you to reach out the Binance Customer Support.

Nevertheless, the Too many requests error can happen when you exceed the rate limits. Each endpoint has an assigned weight, and you’re limited to 6,000 weight requests per minute.
To check the amount of weight already used, you can refer to the x-mbx-used-weight header in the response, which indicates the weight consumed by the current IP.
For more details, take a look at this: General Info | Binance Open Platform