Choosing an API
How to choose a background check API
Every vendor says the integration is easy. The differences show up after your first thousand providers.
- Hosted consentIn your brand, with live IDAsk
- Database hitsConfirmed at the court?Ask
- StatusWhich court, and when?Ask
- SandboxWithout a sales call?Ask
Eight questions decide most of it
Ask every vendor the same ones, in writing.
Price and coverage lists look alike from vendor to vendor. These eight questions are where your engineers and your ops team will feel the difference. The rest of this guide takes them one at a time.
Ask every vendor
The eight questions
- Hosted consent, or build your own?
- A database hit: confirmed or raw?
- Can you see why a check is waiting?
- Who prepares the notices and letters?
- Are contractors covered the same way?
- Can agents use it, with scoped keys?
- Sandbox without a sales call?
- Is a named person on the report?
Hosted consent saves the riskiest screen
The disclosure and consent screens are where onboarding flows most often go wrong.
Building your own consent screens means owning the disclosure wording and the order of each step. Roster hosts disclosure and consent in your brand, with the live ID step after it, and fires check.consent_signed when the provider has signed. What the flow must show.
A database hit should be confirmed at the court
Ask what happens between a possible match and the report.
National databases are a starting point: names collide and records go stale. A typical screening vendor may report a database hit as it comes back. On Roster, a named analyst matches every possible record to the person and confirms it at the court before it’s reported, on every package. The analyst signs the report.
Jordan LeeExample
An analyst is checking a possible record. Nothing is reported until it’s confirmed.
Ops shouldn't have to chase status
Ask whether you can see which court a check is waiting on.
A status of pending tells your support team nothing. Roster reports status by API, webhook and MCP, and explain_status returns one plain sentence, naming the court and a rough time, that you can pass straight to the provider. Questions about a report go to the analyst who ran it.
Ask who prepares the notices and letters
And who sends them, and who decides.
Some vendors hand you a report and stop there. Roster prepares state notices for the provider’s state and the pre-adverse and adverse letters with the waiting-period dates filled in, and keeps a record of every check. Your team sends them and makes every decision: that part stays with you whichever vendor you choose.
- Disclosure and consentHosted, with live IDSigned
- State noticeFor the provider’s stateReady
- Pre-adverse and adverse lettersDates filled in, if neededIf needed
- Record of the checkEvery step, datedKept
Contractors, agents and a sandbox
Three quick checks that rule vendors in or out.
Ask whether contractors get the same notices and letters as employees; on Roster they do. Ask whether your agents can order checks and explain delays with a key scoped to status only, and what they can’t do: on Roster, no agent can sign consent or approve adverse action. And ask for sandbox keys today: Roster’s come without a sales call.
A name on the report
Ask who stands behind each report, and whether you can reach them.
When your ops lead has a question about a record, they need a person, not a ticket queue. Every Roster report is signed by the analyst who confirmed the records, and questions go to that analyst.

What you still own, whichever vendor you pick
A vendor prepares. Your team decides.
You decide why you screen and set the criteria. Your team sends the notices, makes the final call on every provider, and answers to your providers for it. Pick the vendor that makes those jobs easiest to do well.
Test the answers in the sandbox
One call starts a check. See every answer above for yourself.
Sandbox keys come without a sales call. Start a check with POST /v1/checks, open the hosted consent, watch the webhooks, and ask explain_status where it stands, all this afternoon. 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.
Reviewed November 6, 2026 by Dennis Drellishak, Owner. Markdown version.