Handle Checkr webhook events for background check completion and adverse action
domain: checkr.com · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Register a webhook endpoint URL in Checkr Account Settings > Developer Settings > Webhooks section
Listen for the report.completed event, which fires when a background check report is ready; the payload includes report_id and status
For candidates requiring adverse action, call GET https://api.checkr.com/v1/reports/{report_id} to retrieve the full report before initiating the adverse action flow
Initiate adverse action by POSTing to https://api.checkr.com/v1/adverse_actions with the report_id; this triggers Checkr to send the pre-adverse notice and copy of the report to the candidate
Listen for the adverse_action.pre_adverse_action_sent and adverse_action.post_adverse_action_sent webhook events to track the workflow state
Known gotchas
The pre-adverse notice requires a legally mandated waiting period (commonly 5 business days) before post-adverse action can be sent; attempting to send post-adverse action too early via the API may return an error
Webhook payloads must be verified using HMAC-SHA256 with your webhook secret before processing; Checkr includes the signature in the X-Checkr-Signature header
Some jurisdictions (e.g., Los Angeles, New York City) require individualized assessment steps in the adverse action flow; Checkr auto-detects these based on candidate location and adjusts the flow, which may change expected webhook event sequences
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?