Initiate a background check via the Checkr API using candidate invitations
domain: checkr.com · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Authenticate all requests with HTTP Basic Auth using your Checkr API key as the username and an empty password
Create a candidate record by POSTing to https://api.checkr.com/v1/candidates with at minimum email, first_name, and last_name fields
Note the id from the response — this is the Checkr candidate id
POST to https://api.checkr.com/v1/invitations with candidate_id and package fields (the package slug identifies the background check type configured in your Checkr account)
Retrieve the invitation_url from the response and send it to the candidate; they complete identity and consent steps through the Checkr-hosted flow
Known gotchas
The package slug must exactly match a package configured in your Checkr account; an unrecognized slug returns a 404 rather than a descriptive validation error
Checkr operates separate staging and production environments with different base URLs (api.checkr-staging.com vs api.checkr.com) and separate API keys; production keys do not work against the staging environment
Creating a candidate with an email that already exists in your Checkr account does not return an error; it silently returns the existing candidate record, so check the returned id before proceeding
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?