Screen a whole list against every US registry.
Upload a CSV and every person on it is searched across all 58 US registries at once. Each row comes back clear or review, and the whole run is stored as your audit trail. No code needed — and a batch API when you want one.
From spreadsheet to screened, in minutes
Bring the file you already have
A header row with names is enough — firstName and lastName, plus dob, city, state or zipcode when you have them. Your own columns, like a case number or a note, ride along untouched, so an export from your applicant system usually works as-is.
Every row is one search
Each person on the list is searched across all 58 US registries — the same nationwide search you would run one at a time, priced the same way: one metered search per row, stated up front before anything runs.
Read the answers at a glance
Every row comes back marked clear or review, with the match count and the top match beside it. Rows that need eyes stand out; rows that are clear say so in words. The full profiles — photographs, records, official links — are one click away.
Keep the whole run on file
The batch lands in your search history like everything else: who was screened, when, and what came back — the audit trail your next review will ask for.
The same batch, as one API call
POST the CSV itself — or JSON — and get one scored result per row, in order. Same engine, same records, same per-search pricing as the dashboard.
curl https://api.offendersearch.app/v1/batch \
-H "X-API-Key: $OFFENDERSEARCH_KEY" \
-H "Content-Type: text/csv" \
--data-binary @applicants.csvBatch screening questions
How is a batch billed?
Per search, not per file. A CSV of 100 people is 100 metered searches at the normal per-search rate, and the dashboard tells you the exact count before you run it — never a surprise on the invoice.
What columns does the CSV need?
A header row, and at minimum a name per row. Any query field the API accepts works as a column — firstName, lastName, dob, age, city, state, zipcode and more — and a per-row freshness column is honoured. Columns we do not recognise are ignored rather than rejected, so your internal IDs can stay in the file.
How big can a list be?
Up to 1,000 rows per upload in the dashboard, and larger volumes through the batch API. If you screen tens of thousands at a time, talk to us about enterprise terms.
Can developers do this through the API?
Yes — POST the same CSV (or JSON) to the batch endpoint and get one result per row, in order, with the same scored records the dashboard shows. It is the same engine either way.
Can I use batch results for hiring or housing decisions?
Offendersearch is not a consumer reporting agency and results are not a consumer report, so they must not be used for FCRA-covered decisions without appropriate process. Use is subject to our acceptable-use terms and applicable law.
Your list, screened before lunch
Sign up, upload the CSV you already have, and read the answers row by row. 25 free searches to try it on a real slice of your list.