API Throttling Suggestions

Symptom

If a message containing "ces.0429" or "Too Many Requests" is returned when you call an API, it indicates that you have sent too many requests within a short period of time, exceeding the API rate limit. In this case, you can try the following solutions.

Solution

1. Reduce the request frequency. This is the most straightforward solution. Adjust your application (for example, by increasing client-side caches) to send requests at reasonable intervals based on the API's rate limit, avoiding bursts of requests in a short period.
2. Increase the request timeout. If API requests require long processing time, increase the client-side request timeout to allow sufficient time for the server to complete processing. This helps prevent the 429 error caused by timeouts.
3. Use the exponential backoff policy for retries, instead of retrying immediately when encountering error 429. Wait a short time (for example, 1 second) after the first failed retry. Wait longer (for example, 2 seconds) for the second retry. Wait even longer (for example, 4 seconds) for the third retry, and so on, until the retry is successful or the maximum allowed limit on retries is reached. This effectively prevents excessive API requests in a short time.
4. Check the request parameters and headers. Ensure they are correct to avoid server-side processing errors due to invalid inputs.
5. Apply for a higher quota. If your business grows rapidly and the current quota cannot meet the demand, submit a service ticket to contact technical support for assistance in service scenario evaluation and quota increase application. Cloud Eye will provide you with a proper solution based on your actual call requirements.

By implementing these solutions, you can effectively resolve 429 errors returned by APIs and maintain normal application operation.