Certn · Rate Limits

Certn Rate Limits

Certn does not publish fixed numeric per-minute or per-day rate limits for its REST API in the public developer documentation. In practice the API is order-oriented (you create applications and poll or receive webhooks for results) rather than high-frequency, so throughput is effectively governed by your account configuration and the pace at which checks are ordered rather than a documented request cap. Webhook delivery has a defined retry policy: on a 408, 500, 502, 503, or 504 response from your endpoint, Certn retries up to three additional times with increasing back-off between attempts.

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

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

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

Tagged areas include Background Checks, Screening, Rate Limiting, Quotas, and Webhooks.

3 Limits Throttle: 429
Background ChecksScreeningRate LimitingQuotasWebhooks

Limits

REST API Requests account
requests
not published
No fixed numeric request-rate limit is documented for the Certn REST API.
List Pagination request
records
paginated via offset/limit
Applicant/report list endpoints return results in paginated pages.
Webhook Delivery Retries webhook
attempts
3 additional retries
On 408/500/502/503/504 from your endpoint, Certn retries up to three more times with increasing back-off.

Policies

Webhook Retry and Back-off
Failed webhook deliveries (408/500/502/503/504) are retried up to three additional times, waiting longer between each call; other 4xx responses trigger immediate back-off without retry.
Signature Verification
Each webhook carries a Certn-Signature header (HMAC-SHA256 over timestamp + payload) with a fresh timestamp per attempt to prevent replay; verify with constant-time comparison.
Backoff Strategy
Clients should implement exponential backoff with jitter and honor Retry-After if a 429 is returned.

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/certn-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 email required.

GitHub Google LinkedIn

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