# How to choose a background check API

> For a marketplace, the questions that matter are who hosts consent, what happens when a database search finds a possible record, how you see status, who prepares the notices and letters, and whether contractors, agents and a sandbox are covered. Ask each vendor the same eight questions and test the answers in their sandbox before you sign.

By Dennis Drellishak, Owner. Last reviewed November 6, 2026.

## 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.

Eight questions to ask every vendor: hosted consent or build your own; whether a database hit is confirmed at the court or reported raw; whether you can see why a check is waiting; who prepares the notices and letters; whether contractors are covered the same way; whether agents can use it with scoped keys; whether there's a sandbox without a sales call; and whether a named person is 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](https://www.rosterchecks.com/guides/consent-and-disclosure-in-your-onboarding-flow/).

## 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.

Example report row for Jordan Lee, a made-up provider: county criminal, Franklin County, Ohio, confirming at the court. Nothing is reported until an analyst confirms it.

## 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.

Prepared on every check: hosted disclosure and consent with live ID, signed; the state notice for the provider's state, ready; pre-adverse and adverse letters with the dates filled in, if needed; and the record of the check, kept.

## 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.

A quiet analyst desk in a Cleveland office: a printed report with a pen, reading glasses, a desk phone and a paper folder by a window with soft gray daylight.

## 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](https://www.rosterchecks.com/sandbox/) or [read the developer page](https://www.rosterchecks.com/developers/).

---

HTML version: https://www.rosterchecks.com/guides/how-to-choose-a-background-check-api/
