Coming soon. We aren’t taking orders yet.

Choosing an API

Questions to ask before you switch background check vendors

Switching vendors feels risky when onboarding can't stop. Most of the risk is in a few questions you can answer first.

Finish the checks you've started where they started

Let open checks and open adverse actions finish with your current vendor.

Pick a cutover date and send new checks to the new vendor from that day. Checks already running, and any pre-adverse waiting periods already counting down, finish with the vendor that started them. That keeps every letter tied to the report it was based on.

  1. FirstBuild in the sandboxTest providers
  2. ThenCredentialing callLive keys
  3. New checksCutover dateGo to Roster
  4. Old vendorOld checks finishLetters included

Decide where historical reports will live

Old reports stay with the vendor that ran them. Keep your own copies.

Ask your current vendor how long you can reach past reports and how to export them before your contract ends. Roster’s record starts with the first check it runs, with a report page and PDF for each one. Keep exported reports under your own retention policy.

Before your contract ends

Ask your current vendor

  • How long can we open past reports?
  • Can we export the PDFs in bulk?
  • Who answers disputes on old reports?
  • When do open checks need to finish?

Map your webhooks and statuses

Three events cover a Roster check. Map each to what your app does now.

Roster sends check.consent_signed when the provider signs and confirms their ID, check.updated as each search moves, and check.completed when the analyst signs the report. Each delivery is signed in the Roster-Signature header and carries status only, never record details. Map those to the states your onboarding screens already show.

  1. check.consent_signedProvider signed and confirmed IDEvent
  2. check.updatedA search movedEvent
  3. check.completedReport signed by the analystEvent

What Roster prepares from day one

Consent, notices, letters and a record of every check, from the first one.

Hosted disclosure and consent with the live ID step, state notices for the provider’s state, pre-adverse and adverse letters with the waiting-period dates filled in, and a record of every check. A named analyst confirms any possible record at the court, and explain_status tells ops which court a check is waiting on.

What you still own through the switch

The criteria, the letters on old checks, and every decision.

Your criteria move with you: decide whether anything changes, and write it down. Your team sends the letters on checks that finish with the old vendor, sends the ones Roster prepares on new checks, and makes every final call.

Test the whole switch in the sandbox

Consent, live ID, webhooks and the MCP server, with test providers.

Sandbox keys come without a sales call. Point a branch of your app at the sandbox, run test providers through consent and live ID, check your webhook handler against all three events, and try the MCP server with a status-only key. Get sandbox keys or read the developer page.

What Roster handles

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.