Prove · Rate Limits

Prove Rate Limits

Prove does not publish specific numeric rate limits for the v3 API. Throughput is governed per client / per contract and enforced server-side; OAuth 2.0 access tokens obtained from /token are short-lived and must be refreshed, which also paces request volume. The v3 verification flow is stateful and ordered (start -> validate -> challenge -> complete) and bound to a correlation ID, so calls are naturally sequenced per session. Specific per-endpoint values are not reconciled in this artifact.

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

It captures 4 rate-limit definitions, measuring requests, seconds, attempts, and identities.

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

Tagged areas include Identity Verification, Authentication, Phone Intelligence, KYC, and Fraud Prevention.

4 Limits Throttle: 429
Identity VerificationAuthenticationPhone IntelligenceKYCFraud PreventionRate LimitingQuotasThrottling

Limits

Per-Client Request Rate client
requests
see provider documentation
Governed per client/contract; not publicly published.
Access Token Lifetime client
seconds
short-lived (expires_in returned by /token)
Bearer tokens expire and must be reissued via the client-credentials grant.
OTP Retry session
attempts
controlled by allowOTPRetry
Number of one-time-passcode retries is bounded per Pre-Fill / Unify session.
Batch Enroll Size request
identities
100
POST /v3/identity/batch enrolls up to 100 identities per request.

Policies

Contractual Limits
Effective limits are set per client agreement rather than a public tier.
Backoff Strategy
Clients should implement exponential backoff with jitter and honor Retry-After on 429 responses.

Sources