Bulk sex offender search for a whole list of names.
Send up to 1,000 names to POST /v1/batch and every name is searched across all 58 US sex offender registries at once, one result per row, in the order you sent it. No code needed: upload the same list as a CSV in the dashboard, see each row clear or review, and the whole run is kept as your audit trail.
$0.15 a search, $0.11 past 2,000 a month. 1,000 rows per call or upload; 25 free searches.
Screening for criminal records as well? Bulk criminal record search ›
POST /v1/batch { "queries": [ { "firstName": "Jane", "lastName": "Roe", "dob": "1985-07-30", "state": "TX" }, … up to 1,000 rows ] }
// 200 OK · one result per row, in order { "count": 1000, "results": [ { "index": 0, "status": "complete", "counts": { "records": 1, "sourcesIncomplete": 0 }, "records": [ { "matchState": "dob_match", "matchConfidence": 0.97 } ] }, { "index": 1, "status": "complete", "counts": { "records": 0, "sourcesIncomplete": 0 }, "records": [] }, … ] }
Bulk sex offender check, step by step. From spreadsheet to screened, in minutes: bring the file you already have, read the answers at a glance.
Bring the file you already have
A header row with names is enough. Add dob, city, state or zipcode when you have them. An export from your applicant system usually works as is.
Every row is one search
Each person is searched across all 58 US registries, the same search you would run one at a time, priced the same way and stated up front.
Read the answers at a glance
Every row comes back clear or review, with the match count and the top match. Full profiles, photographs and official links are one click away.
Keep the whole run on file
The batch lands in your search history: who was screened, when and what came back. The audit trail your next review will ask for.
No code: the dashboard CSV upload runs the same batch.
Bulk sex offender search, worked example. What goes in, and what comes back: a three-row file and the answer for each, with your case_id beside it.
# applicants.csv 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.
Sex offender batch CSV format: 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. Columns we don’t recognise are ignored, not rejected, so an export from your applicant or admissions system usually works without editing.
| 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. |
Bulk sex offender search limits, stated up front: 1,000 rows per upload or API call, and a bad row never sinks the batch.
Rows per upload
dashboard CSV upload
Rows per API call
split longer lists
Formats
or a queries array with shared settings
A failed row
status: error; the rest still run
Mode
verify single rows Live afterwards
Bulk sex offender search pricing. 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. 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 on search. Your first 25 searches are free.
See pricing ›| 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 |
Who runs bulk sex offender checks. One upload, whatever the list is.

Skilled nursing and senior living
Screen a referral census or a new admission list before beds are offered.
Nursing home screening ›Landlords and property managers
Clear a stack of rental applications, or a whole portfolio, in one pass.
Tenant screening guide ›Nonprofits and youth programs
Run a season of volunteer sign-ups against every US registry at once.
Volunteer screening guide ›HR and staffing teams
Screen a hiring list or an agency roster alongside your other checks.
Employee screening ›Bulk sex offender search API: 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. Screening for criminal records as well? The same file goes to the criminal batch: bulk criminal record search.
curl https://api.offendersearch.app/v1/batch \ -H "X-API-Key: $OFFENDERSEARCH_KEY" \ -H "Content-Type: text/csv" \ --data-binary @applicants.csv
// 200 OK { "count": 3, "results": [ { "index": 0, "status": "complete", "counts": { "records": 1 }, "records": [ { "matchState": "dob_match", "matchConfidence": 0.97, "sources": [ { "jurisdiction": "TX" } ] } ] }, { "index": 1, "status": "complete", "counts": { "records": 0 }, "records": [] }, { "index": 2, "status": "complete", "counts": { "records": 0 }, "records": [] } ] }
Bulk sex offender search questions. Billing per row, list size and the no-code upload.
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.
Screen a list of names for sex offenders. 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.