Truv · Rate Limits

Truv Rate Limits

Truv's REST API is authenticated per-account with the X-Access-Client-Id and X-Access-Secret header pair. Truv does not publish specific numeric rate limits in its public documentation; limits are enforced per access key and coordinated with customers as part of the commercial agreement. Long-running verification work is asynchronous - clients create a link, poll link/report endpoints or subscribe to webhooks, rather than holding a request open. Specific per-endpoint values are not reconciled here.

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

It captures 3 rate-limit definitions, measuring requests, links, and events.

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

Tagged areas include Payroll, Income Verification, Employment Verification, Consumer Permissioned Data, and Rate Limiting.

3 Limits Throttle: 429
PayrollIncome VerificationEmployment VerificationConsumer Permissioned DataRate LimitingQuotasThrottling

Limits

Requests Per Access Key account
requests
see provider documentation
Enforced per X-Access-Client-Id; not publicly published.
Concurrent Links account
links
see provider documentation
Number of in-flight consumer connections; coordinated with the account.
Webhook Delivery account
events
not applicable
Events are pushed to the configured webhook URL; retried on failure.

Policies

Prefer Webhooks
Subscribe to webhook events (login, task/verification completion) rather than polling report endpoints to reduce request volume.
Backoff Strategy
Clients should implement exponential backoff with jitter and honor Retry-After on 429 responses.
Asynchronous Verification
Verification is asynchronous - create a link, then read the report once the associated task completes rather than blocking on a single request.

Sources