Accurate Bg Rate Limits
Accurate Background does not publish fixed numeric rate limits for the Accurate API (v3) in its public developer documentation. In practice, request throughput is a control-plane concern (creating candidates, placing orders, polling status), while the meaningful throughput is the volume of background screenings ordered, which is governed by the account's screening services agreement rather than a per-minute request cap. Standard HTTP semantics apply, and consumers should implement retry-with-backoff and rely on webhooks instead of tight polling for order/report status.
Accurate Bg Rate Limits is the machine-readable rate-limit profile for Accurate Background on the APIs.io network, in the API Commons Rate Limits shape.
It captures 3 rate-limit definitions, measuring requests, screenings, and bytes.
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 2 backoff/retry policies defined and response codes documented for throttled.
Tagged areas include Background Checks, Employment Screening, Rate Limiting, and Quotas.
generated, dated 2026-07-03.
Limits
Policies
Sources
- https://accurate.readme.io/reference
- https://developer.accuratebackground.com/
- https://accurate.readme.io/docs/api-and-http-actions
Work with this as data
Every rate limit here is available over the APIs.io API and to AI agents over MCP.