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, in the API Commons Rate Limits shape.

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

An exhausted limit returns HTTP 429.

This profile was written by API Evangelist and has not been verified against a page the provider published; treat every limit as unconfirmed until a dated transcription replaces it.

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 Exhausted: HTTP 429
Method: generated, dated 2026-07-01.
Written by API Evangelist on 2026-07-01 and not verified against a page the provider published. Treat every limit as unconfirmed until a dated transcription replaces it.
View Source
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

Work with this as data

Every rate limit here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for rate limits

4 MCP tools reach this
  • find_rate_limitsBrowse and filter every rate limit in the catalog.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This rate limit 
curl "https://apis.io/api/v1/rate-limits/truv-rate-limits"
All rate limits 
curl "https://apis.io/api/v1/rate-limits?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.