The sex offender API, 58 US registries in one call.
Send a name and a date of birth to POST /v1/search; get scored, cited registry records back from 57 US registries in one JSON response. $0.15 a call, 25 free, no card.
Updated November 8, 2026 · API changelog
Part of the background check API; jail, court and prison records come from the criminal records API on the same key.
curl -X POST "https://sandbox.offendersearch.app/v1/search" \ -H "X-API-Key: $OFFENDERSEARCH_TEST_KEY" \ -H "Content-Type: application/json" \ -d '{ "query": { "firstName": "Exact", "lastName": "Match", "dob": "1980-01-01" } }'
What comes back from a sex offender API search
The complete captured answer for the sandbox's date-of-birth-verified person, each field explained beside it, then the shape of a clear.
200 OK · scenario “Exact match, date of birth verified” · query {"firstName":"Exact","lastName":"Match","dob":"1980-01-01"} · click to fold
{ "searchId": "srch_sbx_so_exact", "status": "complete", "elapsedMs": 236, "counts": { "records": 1, "sourcesQueried": 58, "sourcesIncomplete": 0, "sourcesComplete": 58, "sourcesSkippedByScope": 0, "recordsReturned": 1 }, "capped": false, "cappedReason": null, "cappedLimit": null, "cappedOmittedSources": [], "omittedFields": [], "page": 1, "perPage": 1, "totalPages": 1, "proof": { "status": "none" }, "warnings": [], "sourceStatus": [ { "source": "AK", "status": "complete", "matched": 0, "fromCache": true, "note": null, "incomplete": false, "incompleteReason": null, "cappedOmitted": false }, { "source": "OH", "status": "complete", "matched": 1, "fromCache": true, "note": null, "incomplete": false, "incompleteReason": null, "cappedOmitted": false }, /* … 56 more rows, every one "status": "complete", "matched": 0 */ ], "records": [ { "recordId": "rec_28db9639d712c4c61e8e", "personRef": "prs_28db9639d712c4c61e8e", "uuid": "SBX-OH-100001", "recordType": "sex_offender", "matchConfidence": 0.9, "matchBasis": [ "lastName", "firstName", "dob", "lastName:exact", "firstName:exact", "name_match" ], "matchDetail": { "strategies": { "lastName": "exact", "firstName": "exact" }, "fieldsPresent": [ "lastName", "firstName", "dob" ], "signals": [ "matchedLegalName" ], "matchedNameType": "legal", "verification": "dob_match" }, "matchedName": { "value": "Exact Sample Match", "type": "legal" }, "name": { "first": "Exact", "middle": "Sample", "last": "Match", "suffix": "", "full": "Exact Sample Match" }, "aliases": [], "nicknames": [], "dob": "1980-01-01", "birthYear": 1980, "dobPrecision": "exact", "age": "46", "sex": "M", "race": "White", "ethnicity": "Not Hispanic", "height": "5'10\"", "weight": "180 lbs", "eyeColor": "Brown", "hairColor": "Brown", "marks": "Tattoo, left forearm (sample)", "addresses": [ { "type": "residence", "line1": "100 Sample St", "city": "Sampleville", "county": "Sample", "state": "OH", "zipcode": "00000", "lat": null, "lng": null }, { "type": "employment", "line1": "200 Example Ave", "city": "Sampleville", "county": "Sample", "state": "OH", "zipcode": "00000", "lat": null, "lng": null } ], "registrationState": "OH", "addressStates": [ "OH" ], "offense": { "crime": "Sexual battery", "statute": "SAMPLE 2907.03", "tier": "Tier III", "convictionDate": "2004-05-12", "offenseDate": "2003-11-02", "registrationDate": "2008-02-01", "releaseDate": "2008-01-15", "caseNumber": "SBX-2003-000101", "victimAge": "Minor", "convictionCounty": "Sample" }, "offenses": [ { "crime": "Sexual battery", "statute": "SAMPLE 2907.03", "tier": "Tier III", "convictionDate": "2004-05-12", "offenseDate": "2003-11-02", "registrationDate": "2008-02-01", "releaseDate": "2008-01-15", "caseNumber": "SBX-2003-000101", "victimAge": "Minor", "convictionCounty": "Sample" } ], "stateData": { "status": "Active", "designation": "Tier III sex offender", "lawAgency": "Sample County Sheriff's Office", "complianceStatus": "compliant", "isLifetimeRegistration": true, "lastVerificationDate": "2026-09-01", "registrationDuration": "Lifetime" }, "flags": { "absconder": false, "predator": false }, "images": [ { "url": "https://sandbox.offendersearch.app/v1/sandbox/photos/1.svg" } ], "housingStatus": "housed", "source": { "jurisdiction": "OH", "registryName": "Sandbox sample registry (OH)", "recordUrl": "https://offendersearch.app/docs/sandbox", "personRef": "prs_28db9639d712c4c61e8e", "recordedAt": "2025-01-10T00:00:00+00:00", "lastCheckedAt": "2026-10-01T00:00:00+00:00", "sourceUpdatedAt": "2026-10-01T00:00:00+00:00" }, "sources": [ { "jurisdiction": "OH", "registryName": "Sandbox sample registry (OH)", "recordUrl": "https://offendersearch.app/docs/sandbox", "personRef": "prs_28db9639d712c4c61e8e", "recordedAt": "2025-01-10T00:00:00+00:00", "lastCheckedAt": "2026-10-01T00:00:00+00:00", "sourceUpdatedAt": "2026-10-01T00:00:00+00:00" } ], "dobVerification": "dob_match", "matchState": "dob_match", "unverified": false } ] }
| Field | Type | What it tells you |
|---|---|---|
| matchState | enum | How the birth information verified: dob_match, year_match, age_match, no_dob_age_year; null when the request sent no date of birth |
| matchConfidence | 0–1 | How much identity evidence the record carries. You choose the threshold; the sample scores 0.9 on name plus date of birth |
| matchBasis · matchDetail | array · object | Which fields agreed and by which strategy (exact, nickname, prefix, fuzzy, alias); matchedName.type says whether a legal name or an alias matched |
| unverified | bool | True when no birth information confirmed the person. A name-only hit on a common surname is a lead, never an identification |
| dobPrecision | enum | exact, year_month, year or unknown: how much of the date the registry publishes |
| offenses[] | array | Every offense with crime, statute, tier, conviction and offense dates, case number and victim age where the registry publishes them |
| stateData | object | Registry-specific fields kept as published: status, designation, compliance status, last verification date, registration duration |
| addresses[] | array | Typed residence, employment and school addresses with county and coordinates where geocoded; addressStates lists the states they fall in |
| registrationState | code | The registry that holds the person, which can differ from where they live; query.state filters on residence and never on this |
| housingStatus | enum | housed, homeless or incarcerated, normalised from the different ways registries write it |
| flags · images[] | object · array | Absconder and predator flags where published, and the registry photographs so a reviewer can compare a face |
| sources[] | array | Jurisdiction, registry name, the registry’s own recordUrl, lastCheckedAt and sourceUpdatedAt: the citation you keep beside a decision |
| personRef | id | A stable reference to the person that survives a registry re-issuing its own record id; monitors and FCRA orders use it |
| sourceStatus[] · counts | array · object | One row per registry in scope. sourcesComplete below sourcesQueried means the answer is a lower bound, and status says partial |
200 OK · scenario “Clear visitor” · query {"firstName":"Clear","lastName":"Visitor"} · click to open
{ "searchId": "srch_sbx_so_clear", "status": "complete", "elapsedMs": 0, "counts": { "records": 0, "sourcesQueried": 58, "sourcesIncomplete": 0, "sourcesComplete": 58, "sourcesSkippedByScope": 0, "recordsReturned": 0 }, "capped": false, "cappedReason": null, "cappedLimit": null, "cappedOmittedSources": [], "omittedFields": [], "page": 1, "perPage": 0, "totalPages": 1, "proof": { "status": "none" }, "warnings": [], "sourceStatus": [ { "source": "AK", "status": "complete", "matched": 0, "fromCache": true, "note": null, "incomplete": false, "incompleteReason": null, "cappedOmitted": false }, /* … 57 more rows, all "complete" */ ], "records": [] }
A clear and a hit share one envelope. Only records and counts.records differ; sourceStatus still carries a row per registry, which is what lets software trust an empty list. Read status first: partial means a registry did not answer and the list is a lower bound. The other test people are on the sandbox page.
How matchState and matchBasis explain a registry match
Three match modes you choose, and two fields on every record that say how the person was identified, so a shared name never reads as a match on its own.
Exact names only. Surname and given name must equal what you sent. For automated accept with no reviewer.
Nicknames, variants, initials, one-letter typos. The default. A first name of Bob finds Robert; the surname stays exact; an age is compared within ageTolerance, one year unless you change it.
Prefix and typo on the surname as well. For a reviewer who would rather see too much than too little.
drop or flag. A record whose published age contradicts the date of birth you sent is dropped by default; send flag and it returns labelled age_mismatch.
Send a date of birth whenever you hold one: a common name stops matching everyone who shares it, and a record moves from a lead to an identification. The rules in full: matching and scoring.
| matchState | Birth information | What most teams do |
|---|---|---|
| dob_match | Full date of birth agreed with the registry record | Act on it |
| year_match | The registry publishes a birth year only, and it agreed | Review |
| age_match | The registry publishes an age, within ageTolerance | Review, compare the photo |
| no_dob_age_year | The registry publishes no birth information; name only | Review, compare the photo |
| age_mismatch | The published age contradicts the date of birth you sent | Dropped unless onAgeMismatch is flag |
| null | You sent no date of birth; nothing could verify | Treat as a lead; unverified is true |
matchBasis
lastName:exact firstName:exact dob name_match
matchDetail.strategies
Per field: exact, nickname, prefix, fuzzy or alias, so a reviewer sees why “Jordy” matched “Jordan”.
Your line
Auto-accept dob_match above the matchConfidence you set; everything else goes to a person.
How a sex offender registry search works in three steps
From an empty account to a production key, with the time each step takes.
Create a key
Sign up for a business account and create a key; it answers production searches at once, 25 free. A sandbox test key is minted in the same dashboard. About thirty seconds.
Send one POST to /v1/search
Name plus date of birth in query, the key in X-API-Key. Read status, counts and sourceStatus before the records. Under a minute with the request above.
Route by matchState and go live
Act on dob_match above your own confidence line, send the rest to a reviewer, keep sources[].recordUrl with the decision. Sandbox and production share one response shape, so the switch is the host name.
| Search by | Use it when | Request body |
|---|---|---|
| Name and date of birth | A known person: applicant, resident, volunteer, patient. | { "query": { "firstName": "Exact", "lastName": "Match", "dob": "1980-01-01" } } |
| Name and approximate age | An age but no full birth date. | { "query": { "firstName": "Name", "lastName": "Only", "age": 46, "ageTolerance": 2 } } |
| Name and state of residence | A common name narrowed to people living in one state; the search still runs across the roster. | { "query": { "firstName": "Out", "lastName": "State", "state": "TX" } } |
| Address or ZIP | Who is registered at or near a property. | { "query": { "address": "100 Sample St", "zipcode": "43215" } } |
| Coordinates and radius | Registrants around a school, facility or listing, up to 100 miles. | { "query": { "lat": 40.1, "lng": -83.0, "radiusMiles": 1, "perPage": 200 } } |
| Selected registries | Only some registries, with the skipped ones counted. | { "query": { "firstName": "Multi", "lastName": "State" }, "jurisdictions": ["FL", "GA"] } |
The bodies above use the sandbox’s documented people. Pagination with page and perPage: pagination · keys and headers: authentication · the five-minute version: quickstart.
The 57 registries one sex offender API call searches
50 state registries, DC, 5 territories, the national public site and the tribal registries, listed from the catalogue the search fans out to. Omit jurisdictions and all of them run; name some and the rest are counted as skipped.
jurisdictions and sourceStatus[].source use.Jurisdictions reference ›One chip per registry: its code and matched. All 57 are drawn, none folded; Ohio holds the sample person.
Registries publish differently: a full date of birth or only an age, a tier or a designation, a vehicle list or none. dobPrecision and stateData keep those differences inside the one schema, and GET /v1/sources publishes each registry’s scope and health. Field rates by registry: data coverage; the national public website: NSOPW API.
Is a sex offender API result a consumer report?
Not from the standard key. The same records can be furnished under FCRA Partner Access when a hiring, housing, credit or insurance decision depends on them.
Data API, not FCRA
- For: visitor and volunteer screening, trust and safety, research, monitoring, and software that shows a public record to the person who asked for it.
- Must not decide: whether someone is hired, housed, insured or given credit. The response is a public-records lookup, not a consumer report, and the key is not approved for those uses.
- Example: An admissions desk screens a visitor against the registries before a visit; no hiring, housing or credit decision is involved.
Self-serve: get a key, then POST /v1/search or /v1/criminal/search.
FCRA Partner Access
- Built in: end-user registration with a permissible purpose, consent on every order, the pre-adverse and adverse-action notices with the consumer’s copy, and a consumer portal.
- Disputes: a dispute endpoint; the record is re-checked with the registry or court that holds it, with an outcome inside 30 days, and a correction reaches every partner that received it.
- Example: A screening company furnishes a report an employer or landlord will act on; the order runs the consent, notice and dispute steps.
Under a written agreement: Request FCRA Partner Access.
The records can be the same; the process around them is not. How the program works: FCRA Partner Access · the orders endpoint: FCRA orders API · reference and statute citations: FCRA docs. This page describes the product, not legal advice.
Sex offender API pricing per call and per monitor
One metered rate for a registry search, a lower rate past the monthly threshold, and monthly watches. Nothing else is required to run a search.
| Item | Price | Unit |
|---|---|---|
| Registry search | $0.15 | per call, the first 2,000 in a calendar month |
| Volume rate | $0.11 | per call past 2,000 in a calendar month |
| Free to start | 25 calls | once per account, on production data, no card |
| Sandbox | $0 | 60 calls a minute and 2,000 a day per test key |
| Person monitor | $3.00 | per person a month |
| Location monitor | $10.00 | per location a month |
No minimum on search. The Map API has its own $300 monthly minimum. No seats, no platform fee, no per-state fee; a batch row is billed as one call.
The first 2,000 calls in a calendar month are $0.15 each, every one after that $0.11. The 25 free calls on a new account are not subtracted here. Live re-verification, monitors and FCRA orders are billed separately.
Watch a person for $3 a month or a location for $10; a monitor replaces the monthly re-run of a roster and alerts by signed webhook or email. Registry watches: sex offender monitoring; the same watch over jail, court and prison records: continuous criminal monitoring API. A criminal search on the same key is billed as its own call.
Worked examples by volume: background check API pricing · every rate: pricing.
Where a sex offender registry check sits in software
Three placements, each with the one field or call that differs.
Front-desk visitor screening
One call per check-in with a name and date of birth.
What differs: counts.sourcesComplete equal to sourcesQueried before a clear is shown.
Marketplace and gig onboarding
Check at sign-up, then watch the people who stay instead of re-running the search.
What differs: a POST /v1/monitors person watch; a new record arrives as a signed webhook.
Property and tenant workflows
Who is registered near a listing is a data-API question; whether to rent to an applicant is an FCRA order.
What differs: the FCRA sex offender check API for the application, the radius search for the listing.
Property management ›Sex offender API comparison with Checkr and SearchBug
Published facts only, each cell from the vendor's own pages on the date in the footnote; rows where another vendor does more are kept.
| Aspect | Checkr | SearchBug | OffenderSearch API |
|---|---|---|---|
| What you pay for | A finished consumer report, per report, by package; court and database fees passed through at cost | Prepaid balance of $10 to $5,000, charged per successful query; Criminal Check priced per search | One API call: scored public records for a name and date of birth, in the same HTTP response |
| Published entry price | $29.99 a report (Basic) | Not stated on its public pages | $0.15 a call, $0.11 past 2,000 in a month |
| Free tierwhere another vendor does more | No free trial listed on its pricing page; a staging environment with mocked data is available on request | A sandbox test account with "a limited number of live queries"; the number is not stated | 25 calls on production data, no card; the sandbox at 60 calls a minute, 2,000 a day per test key, nothing billed |
| When nothing is foundwhere another vendor does more | A report is billed whatever it finds | "There is no charge if there is no information found on a query"; a Criminal Check that finds no record still counts as a successful query | A clear answer is a billed call: the response says which sources answered, which is the evidence a clear needs |
| Test environment | a staging environment with mocked data, available once Checkr grants access (api.checkr-staging.com) | Sandbox API test account on request | Self-serve sandbox with documented test people; mint an os_test_ key in the dashboard |
| Rate limit | 1,200 requests a minute across all endpoints; 429 with X-Ratelimit-Limit, -Remaining and -Reset headers | Not stated on its public pages | No published per-key ceiling in production; a 429 with Retry-After only at capacity, never billed |
| Webhooks | webhooks signed with HMAC-SHA256 in an X-Checkr-Signature header; retries every minute for 10 minutes, then every hour for 24 hours | Not stated on its public pages | Async searches post the finished envelope to a webhookUrl; monitor and FCRA deliveries carry X-Offendersearch-Signature (HMAC-SHA256 over t.body), are retried and can be replayed |
| Continuous monitoring | Checkr offers continuous criminal search at $1.70 per individual a month and continuous MVR at $2.50 per driver a month | Not stated on its public pages | $3.00 a month per person, $10.00 per location, alerts by signed webhook |
| FCRA consumer reports | Yes: every report is a consumer report, $29.99 to $94.99 by package | Not stated on its public pages | Through FCRA Partner Access: $4.95 an order, searches and live checks included, no court fees |
Checkr: checkr.com/pricing and docs.checkr.com, read 2026-11-08. SearchBug: searchbug.com/pricing-api.aspx, read 2026-11-08. Each vendor’s pages are the authority on its product and change without notice; a blank is a fact the vendor does not publish, not a zero. A consumer report and a public-records lookup are different products.
Developer resources for the sex offender registry API
The contract, the collection, the agent tooling and the test surfaces.
Sex offender API rate limits and what it does not return
The edges of one key, a real rate-limit body, and what is out of scope.
| Limit | Value |
|---|---|
| Sandbox, per test key | 60 calls a minute, 2,000 a day; nothing billed |
| Production, per key | No published ceiling. A 429 only when the service is at capacity, with Retry-After; a 429 is never billed |
| Records per response | Up to 4,000 in one answer; above that capped: true, and perPage pages through the rest |
| Batch | 1,000 rows a call; a failing row is reported in place and never stops the batch |
| Deadline | deadlineMs bounds the wait for slow jurisdictions; an unanswered one is named in sourceStatus and the answer says partial |
| Endpoints | POST /v1/search; one X-API-Key header |
- No civil cases, no traffic citations. Criminal records only: jail bookings, prison custody, court cases with dispositions, warrants, and the registries.
- No international records. US county, state and federal sources, and the 58 US registries.
- Not a consumer report. A hiring, housing, credit or insurance decision runs as an order through FCRA Partner Access, not through the standard key.
- No SSN on the standard key, no credit, no verifications, no drug or driving records. Scope comes from the name, the date of birth and the places you already hold; only an FCRA order can trace the address history from an SSN.
- No records from the national public website. Each registry is searched in its own right; the national site is a comparison destination, never a source.
- No definitions of our own. Tiers, designations and flags mean what the publishing state says they mean.
Retry rules and backoff: rate limits, retries and idempotency · every status code: errors.
HTTP/1.1 429 Too Many Requests Retry-After: 12 Content-Type: application/json { "detail": { "code": "overloaded", "retryAfterSeconds": 12 } }Nothing was searched and nothing was billed; wait
retryAfterSeconds and send the same request again.Sex offender API questions developers ask
Scope, timeouts, clears, retention, place searches, monitoring, definitions.
Does query.state limit which registries are searched?
No.query.state keeps only people whose address is in that state; the search still runs across the roster, so someone registered by Oklahoma and living in Texas comes back. To search fewer registries, send jurisdictions; the response counts the rest in counts.sourcesSkippedByScope.What happens when a registry does not answer in time?
deadlineMs bounds the wait. A registry that misses it is named in sourceStatus with a reason and status reads partial. If nothing matched and a registry stopped early, the default answer is 504 incomplete_no_results rather than an empty list; send onDeadline: "partial" to receive the partial body instead.Is a search that finds nobody billed?
Yes. A complete answer with zero records is the product: 58 queried, 58 complete, none matched, with the rows to prove it. A429, a 5xx or a refused 422 searched nothing and is never billed.How long can I re-open a search result?
Fourteen days.GET /v1/searches/{searchId}/results returns the stored records in that window at no charge and answers 410 after it. A recordId resolves for the same period; a registry’s own uuid resolves while the registry publishes it. See result completeness.Can I search by address or radius without a name?
Yes, once a payment method is on file; the 25 free calls need a name in every query. Address, ZIP and coordinate searches return everyone registered in the area, up to 4,000 records a response withcapped set when there are more. For a drawn map view, the sex offender map API answers per map request.How does monitoring differ from re-running the search?
A monitor is a standing watch on a person or a place: when a matching registry record appears or changes, an event is posted to your webhook, signed withX-Offendersearch-Signature, or sent by email. Registry alerts: sex offender monitoring; the same watch across jail, court and prison records: continuous criminal monitoring API.Does the API define who is a predator or what a tier means?
No. Where a registry publishes a flag, a tier or a designation it is carried inflags, offenses[].tier and stateData; what each means is defined by that state’s law, and the record links the registry entry so a reviewer can read it there.Sex offender API how-to guides
Runnable tutorials that use this endpoint as the worked example, each against the sandbox.
All guides: Learn APIs by example · reference: developer docs · packages: SDKs and CLI.
Related sex offender API pages
The rest of the developer surface, one anchor per page.
Make the first sex offender API call today
A key in thirty seconds, 25 free calls, and one response shape from the first call to production.