⏳ The number of requests our API can handle in a given time.
The IDVerse API is designed for high volumes of data across our customers. We have applied API rate limits to promote responsible use of our API. Our rate limit is implemented on a per-API key basis with 2000 requests/day (calendar day, not a rolling 24 hrs). Requests could be made with a burst of 500 requests per second.
The rate limit applies for both the "Create a transaction" and "Fetch a transaction (result) JSON" requests.
The perfect Integration (in theory) has 2 API calls per transaction:
One API call to create the tx. The integration should be using the webhook notification to know when a transaction is completed.
And the second API call to retrieve the transaction results.
Please note that we offer other helpful API services which will create additional API calls, such as Data Redaction endpoints.
When an application exceeds the rate limit for our API, you will receive an HTTP 429 Too Many Requests response code. It would only be unblocked after a minute since the last request caused your application to get rate-limited.
If you require a higher rate limit, we are very happy to increase it for your account. Please contact our support team.
💬 We Are Here to Help!
If you encounter an issue, a bug, or require assistance, please contact our support page here to find the solution. Don't forget to provide any important information on the issue.