For engineers
Background checks for engineers
You own the onboarding flow. Add background checks to it this sprint, without learning screening law first.
Request
POST /v1/checks
{
"provider": { "email": "maya@example.com" },
"package": "care_standard"
}Response201 Created
{
"id": "chk_8Rq2",
"status": "consent_sent"
}An example check. Names are made up.
Sandbox to production in an afternoon.
Build the whole flow against test providers, then swap one key.
Sandbox keys come without a sales call, and the sandbox runs every endpoint, webhook and hosted screen. Live keys come after a short credentialing call, because consumer reporting rules mean we confirm who you are and why you screen. Then sk_test_ becomes sk_live_ and nothing else changes.
- Right awaySandbox keyNo sales call
- Same hourFirst test checkPOST /v1/checks
- Same afternoonWebhook handlercheck.completed
- A short callCredentialing callLive keys
- sk_live_ProductionNothing else changes
One call starts a check.
Send the provider’s email and a package. Consent and live ID are hosted in your brand.
The response carries the check id and a consent link. The provider signs and confirms their identity with their ID and a live selfie on their phone; nobody signs for them, and your app never stores the ID.
Behind the call, a named analyst matches every possible record to the person, confirms it at the court, and signs the report. You don’t build any of that.
Request
curl -X POST https://api.rosterchecks.com/v1/checks \
-H "Authorization: Bearer sk_test_…" \
-d '{ "provider": { "email": "maya@example.com" },
"package": "care_standard" }'Response201 Created
{
"id": "chk_8Rq2",
"status": "consent_sent",
"consent_url": "https://checks.yourmarketplace.com/c/8Rq2"
}Webhooks tell you when it moves.
Consent signed, updated, completed. No polling.
Three events cover a check. Each delivery is signed with your endpoint’s secret, and webhooks carry status, never record details.
When a notice or letter is due, the check carries it ready to send with the dates filled in, and a webhook fires when each step is due. Your ops team sends and decides; your code just routes the event.
Request
POST https://yourmarketplace.com/webhooks/roster
Roster-Signature: t=1760620800,v1=5f2b…Response200 OK
{
"type": "check.completed",
"check": { "id": "chk_8Rq2", "status": "cleared" }
}Scoped keys, and an MCP server for your agents.
Each caller gets only the scopes it needs.
Give your backend a key that starts checks and your agents a status-only key. The roster MCP server lets agents start checks, read status and explain a delay with explain_status.
An agent can’t sign consent for a provider, read a report on a status-only key, or take adverse action. What agents can and can’t do.
| Scope | Lets the key |
|---|---|
| checks:write | Start a check and resend consent |
| checks:read | Read status and explain_status |
| reports:read | Open the report and PDF |
Start in the sandbox this afternoon.
Sandbox keys right away, no sales call. Live keys after a short credentialing call.
- One call starts a check. Hosted consent and live ID in your brand; a webhook when it’s done. Sandbox keys without a sales call.
- Status by API, webhook and MCP. explain_status says which court it’s waiting on and when to expect it.
- A named analyst matches every possible record to the provider and confirms it at the court before it’s reported. A signed report page and PDF your team can open.
- Every notice and letter prepared, with the waiting-period dates filled in, and a human approval gate before adverse action.
- You send the notices and make the final call. Contractors covered the same way as employees.