Veriff · Rate Limits

Veriff Com Rate Limits

Veriff does not publish specific numeric API rate limits. The Public API is metered per integration (identified by X-AUTH-CLIENT) and is subject to server-side throttling to protect platform stability. Practical throughput is governed more by the commercial verification volume agreed with Veriff than by a documented requests-per-second ceiling. Callers should handle 429 Too Many Requests responses and back off. Decision data is typically consumed via webhooks rather than by polling the decision endpoint, which keeps request rates low by design.

Veriff Com Rate Limits is the machine-readable rate-limit profile for Veriff on the APIs.io network, conforming to the API Commons Rate Limits specification.

It captures 2 rate-limit definitions, measuring requests and sessions.

The profile also includes 2 backoff/retry policies defined and response codes documented for throttled.

Tagged areas include Identity Verification, KYC, AML, Rate Limiting, and Quotas.

2 Limits Throttle: 429
Identity VerificationKYCAMLRate LimitingQuotasThrottling

Limits

Per-Integration Requests integration
requests
see provider documentation
Enforced per integration (X-AUTH-CLIENT); no public numeric value.
Session Creation integration
sessions
governed by commercial volume
Effective ceiling tied to the agreed verification volume, not a hard RPS.

Policies

Prefer Webhooks Over Polling
Consume Decision and Event webhooks instead of polling the decision endpoint to minimize request volume and avoid throttling.
Backoff Strategy
On 429 responses, implement exponential backoff with jitter and retry the request after a short delay.

Sources