Hello @nabil.hassoumi ,

"Error 429 Too Many Requests" is sent as a response when the user has exhausted the maximum number of API calls per second. The users are advised to send 1 API request per second and exceeding this limit they would receive the error 429. The error depends on the maximum number of API calls per second and the available capacity on the WC1 platform (number of API calls being sent to the WC1 server by all the users at that instance).

In order to deal with this error, please re try the failed API calls after a brief delay and have a mechanism at a client's end to detect 429 error and downscale the number of API calls fired accordingly for better results.

Here is an excerpt from the "Quality of Service" section of our WC1 API documentation for your reference.

"The throttling limits are applied to all requests made by a user of the API, so a HTTP 429 response for one method would require a delay waiting period for all other API requests that may be processing during the same time period, for the same API user. Appropriate error handling that can check for errors such as HTTP 429 and retry requests using a policy such as exponential backoff should therefore be added to all World-Check One API calls.

Requests made to the World-Check One API are rate limited to ensure a consistent experience for all customers, however exact throttling limits may vary over time to adjust for available capacity on the platform. When making requests to the World-Check One API, it is advisable to check for HTTP 429 Too Many Requests response codes and attempt to retry the affected requests after a brief delay."

For more detailed information, I request you to refer the "Quality of Service" section of our documentation.

Thanks,

Irfan Khan.