Checkr · Rate Limits

Checkr Rate Limits

The Checkr API applies a documented account-wide rate limit of 1200 requests per minute across all endpoints. Each response includes X-Ratelimit-Limit, X-Ratelimit-Remaining, and X-Ratelimit-Reset headers so clients can track their remaining budget and the reset time. Requests that exceed the limit return HTTP 429 with the reset timestamp. Checkr also supports idempotent POST requests via an Idempotency-Key header, so retries after a 429 do not create duplicate resources. List endpoints are paginated with page and per_page parameters (default 25 records per page).

Checkr Rate Limits is the machine-readable rate-limit profile for Checkr on the APIs.io network, in the API Commons Rate Limits shape.

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

Limit state is signalled in the X-Ratelimit-Limit, X-Ratelimit-Remaining, and X-Ratelimit-Reset response headers, and 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 Background Checks, Employment Screening, Rate Limiting, and Quotas.

2 Limits Exhausted: HTTP 429 X-Ratelimit-LimitX-Ratelimit-RemainingX-Ratelimit-Reset
Method: generated, dated 2026-07-03.
Written by API Evangelist on 2026-07-03 and not verified against a page the provider published. Treat every limit as unconfirmed until a dated transcription replaces it.
View Source
Background ChecksEmployment ScreeningRate LimitingQuotas

Limits

API Requests account
requests
1200 per minute
Documented account-wide limit across all endpoints; returns 429 when exceeded.
Pagination Page Size request
records
25 default per page
Controlled via the per_page query parameter on list endpoints.

Policies

Throttling
Requests beyond 1200/minute receive HTTP 429 with a reset timestamp; clients should back off until the window resets.
Idempotency
POST requests accept an Idempotency-Key header so retries (including after a 429) do not create duplicate candidates, reports, or invitations.
Backoff Strategy
Clients should implement exponential backoff with jitter and honor the X-Ratelimit-Reset header on 429 responses.

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/checkr-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.