Recruiting & ATS · Integration
Checkr
Add Checkr to your product for your customers, and give your AI agents governed access to it.
Embed a Checkr integration so your customers can run and track their own background checks from inside your product, working candidates, reports, and statuses without a separate portal. This data is sensitive, so access is scoped per tenant, limited to the fields you map, and every read and write is logged, which means your product exposes only what it actually needs. fastn handles each customer's credentials and API upkeep, so onboarding an account is configuration rather than a release.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let customers create candidates and order checks from inside your product, using their own Checkr account.
Read report status and results so hiring progress shows up where recruiters already work.
Map each customer's own packages and required fields so an unusual setup needs no code from you.
Trigger your product when a report is completed, suspended, or its status changes.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
An agent reports where a candidate's check currently stands before a recruiter follows up.
An agent orders a check for a candidate within governed permissions, with the action audited.
An agent reacts to a completed report and advances the candidate in the hiring workflow.
Example prompt
List checks pending for more than five days and show the candidate and package for each.
Set up Checkr in 4 steps
- 01Open the Checkr connector from your fastn dashboard.
- 02Have each customer authenticate their Checkr account with least-privilege credentials.
- 03Map the candidate, package, and report fields your product uses, then enable actions and triggers.
- 04Call them from your product, or expose them to an agent through the MCP server.
Why teams use the Checkr integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a Checkr integration without building it. Your customers connect their own Checkr account inside your product and work their job requisitions, candidates and applications there, with no per-customer code on your side.
- Handle the part that actually costs time: candidate records are personal data with consent and retention rules attached. fastn owns the auth, token refresh, rate limits, pagination and breaking-change fixes, so a Checkr update is not your on-call problem.
- One integration serves your product and your agents. The same governed Checkr connection powers in-product features and gives AI agents scoped, audited access, so you keep hiring pipelines moving without manual re-entry without wiring it twice.
Used by these teams
Works well with
Ceridian Dayforce
Slack
HubSpotOften used alongside
Tools the same teams tend to run next to Checkr, across other categories.
Notion
Box
Docusign
JiraCheckr integration FAQ
How do I add a Checkr integration to my product?
Enable the Checkr connector in your fastn dashboard, then let each customer authenticate their own Checkr account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no Checkr client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own Checkr account?
Yes. Every connection is scoped to the individual customer, so each authorises their own Checkr account and only ever sees their own job requisitions, candidates and applications. That per-tenant isolation is the point of an embedded integration: you support the long tail of customer setups without maintaining an integration per customer.
Can AI agents use this Checkr integration?
Yes. The same connection is exposed to your agents through the fastn MCP gateway, with permissions scoped per tenant and every call audited. An agent reports where a candidate's check currently stands before a recruiter follows up.
Who maintains the Checkr integration?
fastn does. When Checkr changes an endpoint, deprecates a field or alters its auth, the fix lands in the connector rather than in your backlog, and your customers' connections keep working.
How is candidate data from Checkr handled?
Access is scoped per tenant and limited to the fields you map, credentials are encrypted, and every read and write is logged. That matters more here than in most systems, because candidate records are personal data that carry consent and retention obligations.
Can my product react when a candidate's status changes in Checkr?
Yes, through event triggers: a stage move where Checkr owns the pipeline, or a completed assessment, a returned report or a finished reference where it owns one step in it. Events are delivered per tenant and can be replayed after an outage, so a hiring team does not silently lose an update while your product was unreachable.
What can I build with the Checkr integration?
A common starting point: create candidates and order checks from inside your product, using their own Checkr account. Teams also use it for the other use cases listed above, and expose it to agents for governed reads and writes.
How much does the Checkr integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding Checkr does not change your per-connector cost. You can start free with 3 connected accounts.
Add Checkr to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.