Developers
Handling Rate Limiting
When interacting with APIs, adhering to imposed rate limits is crucial to ensure smooth operation and avoid encountering HTTP 429errors (Too Many Requests). iProov has a rate limit of “TPS limit as per your contract” Transactions Per Second (TPS) per Service Provider. This limit is in place to ensure a consistent and reliable service for all of our customers. If you anticipate needing a higher rate limit, please contact us in advance and we can discuss increasing it for you. Accurate volume estimations from customers are essential for iProov to provide the best possible service.
The section discusses the use of a backoff mechanism to mitigate the risk of exceeding a TPS limit and encountering subsequent HTTP 429 errors. The backoff mechanism introduces a delay between consecutive authentication attempts, reducing the likelihood of exceeding the TPS limit. There are several backoff mechanisms available, each with its own characteristics and suitability for different system requirements.
Rate Limited Endpoints:
| Enrol Endpoint | POST https://<base_url>/api/v2/claim/enrol/token |
| Verify Endpoint | POST https://<base_url>/api/v2/claim/verify/token |
| Description | Generate an enrolment token for a new user to enrol with a service provider. Please find the documentation here |
| Error | {"error": "too_many_requests", <br>"error_description": "string"} |
| HTTP Status Code: 429 | The Service Provider rate limit has been reached. |
IMPORTANT: The TPS Limit does not impact at the SDK level, meaning once the user journey has started in the app it will complete successfully.
Some of our suggested mechanisms are detailed below: