Bulk sex offender search for a whole list of names.
Upload a CSV and every name on it is searched across all 58 US sex offender registries at once. Each row comes back clear or review, and the whole run is kept as your audit trail. No code needed — and a batch API when you want one.
Screening for criminal records as well? Bulk criminal record search →
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 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.
What goes in, and what comes back
A three-row file, and the result for each. Your own columns — here a case_id — ride along untouched so you can match answers back to your records.
firstName,lastName,dob,state,case_id
Jane,Roe,1985-07-30,TX,APP-1042
John,Public,1979-02-14,CA,APP-1043
Mary,Sample,1990-11-02,FL,APP-1044| case_id | Name | Result | Matches | Top match |
|---|---|---|---|---|
| APP-1042 | Jane Roe | Review | 1 | dob_match · TX registry |
| APP-1043 | John Public | Clear | 0 | — |
| APP-1044 | Mary Sample | Clear | 0 | — |
Illustration uses fictional data. A Review row means at least one candidate to check by eye — open it for photographs, the offense detail and the official record link. A Clear row found nothing to review across all 58 registries.
Columns the CSV understands
A header row and a last name per row is the only requirement. Everything else narrows the match — send what you hold, leave the rest out.
| Column | Required? | Example | What it does |
|---|---|---|---|
lastName | Required | Roe | The one field every row needs. |
firstName | Recommended | Jane | Narrows matches and raises confidence. |
dob | Optional | 1985-07-30 | The strongest single narrowing field. |
age | Optional | 39 | Use when you have no date of birth. |
state | Optional | TX | Filters where people live, not where we look. |
city / zipcode | Optional | Austin / 78701 | Narrow to a place when that is the question. |
your own columns | Passed through | APP-1042 | Case IDs and notes ride along untouched. |
Columns we don’t recognise are ignored, not rejected — so an export from your applicant or admissions system usually works without editing.
What a list costs
Priced per name, not per file — and the dashboard shows the exact count before a run starts, so the invoice is never a surprise.
| Names in a month | Total | Works out to, per row |
|---|---|---|
| 100 | $15.00 | $0.15 |
| 500 | $75.00 | $0.15 |
| 1,000 | $150.00 | $0.15 |
| 2,000 | $300.00 | $0.15 |
| 5,000 | $630.00 | $0.13 |
| 10,000 | $1,180.00 | $0.12 |
Each row is one search at $0.15. Past 2,000 searches in a calendar month, every further search that month is $0.11. No setup fee, no seats, no minimum. Your first 25 searches are free.
One upload, whatever the list is
Skilled nursing & senior living
Screen a referral census or a new admission list before beds are offered.
Landlords & property managers
Clear a stack of rental applications, or a whole portfolio, in one pass.
Nonprofits & youth programs
Run a season of volunteer sign-ups against every US registry at once.
HR & staffing teams
Screen a hiring list or an agency roster alongside your other checks.
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.csvBulk sex offender search 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. A batch runs in Regular mode against the continuously-updated corpus. 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 1,000 per call through the batch API — split a larger list into files of 1,000 and send them one after another. If you screen tens of thousands at a time, talk to us about volume 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 check criminal records in bulk too?
Yes. Bulk criminal record search runs the same way through the API — the same CSV, the same key, one result per row — across county jail rosters, prison systems, court records, warrants and statewide registries. See bulk criminal record search.
Can I use batch results for hiring or housing decisions?
Standard results are not a consumer report, so they must not be used for FCRA-covered decisions; FCRA-regulated screening runs through FCRA Partner Access. 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.
The Offendersearch APIs
One account, one key, one bill — the sex offender registry and criminal records, side by side.
Sex offender registry
- Sex offender API — One call across 58 US sex offender registries, with scored matches and a citation on every record.
- Sex offender search API — Endpoints, request shapes, record fields, matching and batch, in detail.
- Sex offender database — The national registry data in one schema — photos, aliases, offenses, addresses.
- Registered offender database — What a registered offender record holds, and how its accuracy is measured.
Criminal records
- Criminal records API — County, state and federal records — jail, prison, court and warrant — through one API.
- Criminal background check API — One cited answer per person for onboarding and screening flows.
- Criminal search API — The search endpoint itself: parameters, record types and coverage, call by call.
- Background check API — The registry and criminal layers together, on one key and one bill.
- Employment background check API — The registry and criminal data layer for HR, ATS and screening platforms.
- Bulk criminal record search — Run a list of names against criminal records in one call.
Build with it
- API documentation — Quickstart, every endpoint, the record object and the OpenAPI spec.
- Background check API pricing — $0.15 a call, $0.11 past 2,000 a month, 25 free calls to start — worked out by volume.
- Background check API integration — Keys, the first call, async and webhooks, batch, monitoring and errors, step by step.
- MCP server for offender search — Give Claude and other AI agents the same search as a tool.
- Offendersearch vs offenders.io — A side-by-side comparison of the two registry APIs.