Throttling
IoT Central throttles API requests on a per application basis. This means that once the throttling limit has been reached for an application, subsequent API requests will not succeed, and responses will contain the 429 response code. Throttling is in place to help the performance of the application so that it is accessible to end-users and programmatic clients.
The IoT Central API uses rate-limit throttling, which means it allows a specific number of requests for an application in a defined timespan before throttling. This is enforced across all API tokens and user bearer tokens.
Throttling limits
- Throttling limit: 20 requests per second per application
- Throttled response: 429 Too Many Requests
When your client receives a 429 response code, it should try to back off and send fewer requests concurrently. Try to identify any other clients who may be making API requests at the same time, as these requests may contribute to the throttling limit.
Next steps
Have a suggestion about throttling? Post it on UserVoice
See other common error codes