County criminal search API
Name the county in your own words, ask its court live, and get each case back as JSON: charges, dispositions, dates, the court’s own link and the moment it was checked. Every answer lists the counties that had no court source, so a clear is never a guess.
Updated November 22, 2026 · API changelog
curl -X POST https://api.offendersearch.app/v1/criminal/search \
-H "X-API-Key: $OFFENDERSEARCH_KEY" \
-H "Content-Type: application/json" \
-d '{
"query": { "firstName": "Jordan", "lastName": "Rivera", "dob": "1988-04-12" },
"geography": { "county": "OH:Franklin" },
"recordKinds": ["court"],
"coverage": { "yearsBack": 7 },
"live": { "jurisdictions": [{ "county": "OH:Franklin" }] }
}'County criminal search request: county, ZIP radius, city or state
No jurisdiction codes to look up. Name the place the way your order form already holds it; the server finds the court, jail and agency systems that cover it.
| geography | Example | Covers |
|---|---|---|
county | {"county": "OH:Franklin"} | One county, by name or five-digit FIPS code |
zip | {"zip": "43215"} | Every county the ZIP code touches |
radiusMiles | {"zip": "43215", "radiusMiles": 25} | Adds every county whose center is within 0–100 miles; state lines do not stop it |
city + state | {"city": "Columbus", "state": "OH"} | Every county the city spans |
states | {"states": ["OH", "IN"]} | Whole states, up to 10, with their statewide systems |
Three keys turn a name search into a county criminal search. geography is the place. recordKinds keeps the systems that hold the kind of record you sell: court for a county criminal court search, and jail-roster, doc-inmate, warrant or exclusion when the package includes them. coverage.yearsBack leaves out systems whose stated window is shorter than your search, and lists them.
The fourth key makes it live: the same geography object inside live.jurisdictions asks every county, city and regional system in the area that can answer live. A statewide court or prison system is added by its code from the jurisdictions catalog. The whole option list is in criminal search filtering.
A place that matches no US county is 422 unknown_geography; a malformed one is 422 invalid_geography. Both name the field.
County criminal search response: what was searched and what was not
The coverage block is what a reviewer reads first. It names every system behind the answer and every county that had none.
{
"status": "complete",
"counts": { "records": 1, "filteredOut": { "sources": 2 }, "unknownKept": {}, "quarantined": 0 },
"records": [ { "externalId": "OH-FRANKLIN:booking:2024-00731", "...": "..." } ],
"coverage": {
"geography": {
"asked": { "zip": "43215", "radiusMiles": 25 },
"recordKinds": ["court", "jail-roster"],
"sourcesSearched": 7,
"jurisdictionsSearched": [
{ "code": "OH-FRANKLIN", "name": "Franklin County, OH", "kind": "county",
"recordKinds": ["court", "jail-roster"], "counties": ["Franklin County, OH"] },
{ "code": "OH-DELAWARE", "name": "Delaware County, OH", "kind": "county",
"recordKinds": ["jail-roster"], "counties": ["Delaware County, OH"] },
{ "code": "OH-COURT", "name": "Ohio — statewide court records", "kind": "statewide",
"recordKinds": ["court"], "counties": [] }
],
"counties": [
{ "fips": "39049", "name": "Franklin County", "state": "OH", "sources": ["OH-FRANKLIN", "OH-FRANKLIN-JAIL"] },
{ "fips": "39041", "name": "Delaware County", "state": "OH", "sources": ["OH-DELAWARE"] },
{ "fips": "39097", "name": "Madison County", "state": "OH", "sources": [] }
],
"countiesWithoutSource": [ { "fips": "39097", "name": "Madison County", "state": "OH" } ]
}
}
}ZIP 43215 is in Franklin County, Ohio; 25 miles from its center reaches the neighbouring counties. Franklin has its own court and jail sources. Madison County has none of the asked kinds, so it is listed in countiesWithoutSource: only the Ohio statewide and federal systems stood behind the answer there.
That one list is the difference between a county search you can defend and one you cannot. A clear from a county with no source is a statement about the statewide tier, not the county court, and your report can say so. It is also the hand-off list for a courthouse researcher, which the court runner alternative page builds into a router.
Records for the same name from systems outside the area are counted in counts.filteredOut.sources, never dropped silently.
| Field | Type | What it tells you |
|---|---|---|
| coverage.geography.asked | object | The place you sent, echoed back: a county, a ZIP and radius, a city or states. |
| coverage.geography.jurisdictionsSearched[] | array | Every court, jail and agency system searched, with its kind (county or statewide), the record kinds it holds and the asked counties it covers. |
| coverage.geography.counties[] | array | Every county in the area, by FIPS code and name, with its own local sources. |
| coverage.geography.countiesWithoutSource[] | array | Asked counties with no county, city or regional source of the asked kinds. Only statewide and federal systems stood behind the answer there. |
| coverage.geography.yearsBack | object | With coverage.yearsBack: the sources left out because their stated window is shorter, and how many state no window. |
| sourceStatus[] | array | One row per system asked live: ok, incomplete, incompleteReason, records, live: true. |
| sources[].recordUrl, lastCheckedAt, live | string, datetime, boolean | The court’s own page for the record, when it was checked, and whether that check happened during your request. |
| counts.filteredOut.sources | number | Records for the same name from systems outside the county, counted rather than hidden. |
Instant county criminal search vs a live county check
Two answers from one endpoint. The instant one finds candidates; the live one confirms them at the court before anything is reported.
| Instant (stored answer) | Live at the source court | Courthouse search by a researcher | |
|---|---|---|---|
| Request | No live block | live.jurisdictions with the county | An order to a researcher network |
| Answer time | In the call | In the call for up to two in-request systems; a polled job otherwise | Commonly quoted in business days |
| What it proves | What our copy held at lastCheckedAt | What the court showed during your request (live: true) | What the researcher saw at the counter |
| Price | $0.15 | + $0.02 per system that answered, $2.00 ceiling | A per-county fee plus court access fees |
| Counties with no online court | Listed as gaps | Listed as gaps | Reachable in person |
The instant county criminal search is the screening industry’s database step done properly: a name, a date of birth and a county, answered from our copy with each record’s match state (dob_match, year_match, name_match and the rest) and the time the record was last checked. It is fast and cheap, and it is a pointer, not a report.
The live check is the step that used to need a person at the courthouse. Each system is asked during your request; a record it confirms carries sources[].live: true and a new lastCheckedAt; a stored record it did not return is flagged. The mechanics, the billing and the evidence are on the criminal record verification API page.
Why the date of birth matters: many county indexes publish no birth date, and a name alone is a weak key. The date of birth reference explains how a live check can confirm your date with the court (dobVerification: source_confirmed), and clearances record once that a returned person is not your subject.
Reading a case once it comes back, conviction against dismissal against deferred, is covered in the court records search guide and normalized fields.
County criminal search turnaround, by path
What decides whether a county answer comes back in the call or as a job, and how to build for both.
| Path | HTTP | When | What you do |
|---|---|---|---|
| Stored answer | 200 | No live block | Read the records |
| Live, in-request | 200 | Up to two systems that can answer inside a request | Read the records and sourceStatus |
| Live, as a job | 202 | More systems, or one that cannot answer in-request: most jurisdictions | Poll GET /v1/criminal/searches/{searchId} until 200 |
| FCRA order | 202 | Every order | Webhook order.completed; 90% of criminal checks done in under 30 minutes |
Build the client for 202: the live and async searches reference has the polling loop, and rate limits, retries and idempotency covers backoff. A live system that fails is reported inside the completed result as an incomplete sourceStatus row and is not billed. Industry turnaround in general is compared on how long does a background check take.
County criminal search API coverage by state
Statewide court sources, county jail rosters, prison systems and warrant systems by state. Depth varies by county; the response always shows it.
The twelve states with the most live jurisdictions. Every state links to its criminal records by state page, which lists its counties.
| State | Courts | County jail rosters (live / catalogued) | Prison system | Warrants |
|---|---|---|---|---|
| Kentucky | Statewide | 119 / 121 | Statewide | — |
| Texas | Statewide | 84 / 104 | Statewide | Statewide |
| Ohio | Statewide | 82 / 86 | Statewide | Statewide |
| South Carolina | Statewide | 72 / 73 | Statewide | Statewide |
| Indiana | Statewide | 70 / 74 | Statewide | — |
| Pennsylvania | Statewide | 69 / 71 | Statewide | Statewide |
| California | Statewide | 66 / 71 | Statewide | Statewide |
| New York | Statewide | 65 / 67 | Statewide | Statewide |
| Missouri | Statewide | 66 / 68 | Statewide | — |
| Montana | Statewide | 61 / 72 | Statewide | — |
| Virginia | Statewide | 60 / 62 | Statewide | Statewide |
| Florida | Statewide | 57 / 63 | Statewide | Statewide |
Jurisdictions in our catalogue as of 2026-11-08; a live jurisdiction answers a search today. Approximate, not an official figure. Showing the 12 states with the most live jurisdictions; the full list is in the criminal coverage reference.
Coverage is jurisdiction by jurisdiction, never assumed. The exact list, with each system’s record kinds and window, is GET /v1/criminal/sources in the criminal coverage reference; the state tier on its own is the statewide criminal search, and federal cases are on federal criminal records.
County criminal search on the data API or in an FCRA order
The county records and the live checks are the same on both paths. An FCRA order builds the county list from the address history, re-checks every hit live and withholds what the court no longer shows.
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.
Why a screening company re-checks a county hit before it is reported: FCRA 613 compliance. The order itself: FCRA criminal background check API and the search scope reference.
County criminal search API pricing
A search, the live systems that answered, and nothing for the ones that did not. No court fees.
| Item | Price | Unit |
|---|---|---|
| County criminal search (stored answer) | $0.15 | per call, the first 2,000 in a calendar month |
| Live re-verification | +$0.02 | per completed live source, $2.00 ceiling per search; a source that did not answer is not billed |
| 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 |
| FCRA order | $4.95 | per order; sex offender and criminal court search included, with no court fees or extra charges |
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.
Worked example: an address history with three counties, each searched with two systems answering live, costs 3 × ($0.15 + $0.04) = $0.57. A verification PDF of any search is $0.02. More on the background check API pricing page.
Worked examples by volume: background check API pricing · every rate: pricing.
Limits of a county criminal search API
Rate limits, the response cap, and what a county search cannot return.
| 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/criminal/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 county the court does not put online. A county with no online criminal index is listed in
countiesWithoutSource; a courthouse researcher is still the way to search it. - No sealed or unpublished cases. A live check asks a court about what it lists.
- Live checks are not offered inside a batch.
POST /v1/batchreads the stored answer.
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.County criminal search API questions
Turnaround, coverage, address history and look-back: what a screening company’s engineering team asks first.
Is an instant county criminal search the same as a live one?
No, and the difference matters. The instant answer is our stored copy of the county’s records, returned in the same call for $0.15. A live county search adds a live block, which asks the county’s systems again during the request and marks each record it confirms with live: true. Use the instant answer to find candidates and the live check before anything is reported.
What is the county criminal search turnaround?
A stored answer returns in the call. A live check of up to two systems that can answer in-request also returns in the call (200). More systems, or any that cannot answer in-request, run as a job: 202 with a poll URL. On FCRA orders, 90% of criminal checks done in under 30 minutes.
Do you cover every county?
No, and the response never pretends to. Coverage is built jurisdiction by jurisdiction. Each answer lists every asked county with no court source of its own in coverage.geography.countiesWithoutSource; only statewide and federal systems stood behind the answer there. Those counties need a courthouse researcher.
How do I search the counties in an address history?
Send one search per county (or a ZIP with radiusMiles to sweep the neighbouring counties), or send geography.states for whole states. Several place fields in one geography object combine into one area. For an FCRA order, the order builds the search plan from the address history for you and shows it before it runs.
How far back does a county criminal search go?
As far as each court publishes. Send coverage.yearsBack to leave out sources whose stated window is shorter (they are listed, not hidden), and filters.lookbackYears to keep only records dated inside a window. On FCRA orders the seven-year rules are applied charge by charge.
What happens to a stored record the live check does not return?
It is flagged as not returned by the live check (liveResult "not_found_live", counted per source in notFoundLive), so a reviewer sees the disagreement. An FCRA order never furnishes a record from the stored copy: one the court no longer shows is withheld as not_current_at_source.
Can I run county searches in a batch?
POST /v1/batch runs up to 1,000 rows against the stored answer, billed per row. Live checks are per search, so send the rows that need confirming one at a time with a live block.
Learn the API by example
Runnable guides that use this endpoint as the worked example.
All guides: Learn APIs by example · reference: developer docs · packages: SDKs and CLI.
Related county criminal search API pages
The rest of the developer surface, one anchor per page.
Run a county criminal search against the sandbox
Mint an os_test_ key, send a county with a live block and read coverage.geography. Nothing is billed.
The OffenderSearch APIs
One account, one key, one bill.