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, conforming to the API Commons Rate Limits specification.

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

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 Throttle: 429
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