OffenderSearch
Criminal records API · pay per call · same key as the registry

The Criminal Records API. County to federal, in one call.

POST /v1/criminal/search returns jail bookings, prison custody, court cases with dispositions and warrants for one person as scored, cited JSON from more than 1,900 live county, state and federal jurisdictions, with a first call minutes after sign-up at $0.15 a call.

25 free calls · no card
1,934 live jurisdictions1,782 county jail rosters live54 prison systems48 court sources35 warrant systems
Catalogue as of 2026-11-08; a live jurisdiction answers a search today. Approximate, not an official figure: criminal coverage reference.
POST /v1/criminal/search · sandbox
curl -X POST "https://sandbox.offendersearch.app/v1/criminal/search" \
  -H "X-API-Key: $OFFENDERSEARCH_TEST_KEY" \
  -H "Content-Type: application/json" \
  -d '{
      "query": {
        "firstName": "Felony",
        "lastName": "Record",
        "dob": "1975-06-15"
      }
    }'
One court case: a felony burglary conviction with case number, court, charges, plea, disposition and sentence. DOB-verified.Sandbox people are synthetic; production answers have the same shape.

Updated November 8, 2026 · API changelog

What a criminal records API response contains

One envelope, one record object for every kind and every jurisdiction. The hero shows the sandbox's felony case; these are the fields a first integration reads from it.

A criminal history in the United States is held in pieces. A county court decides most cases and publishes them in its own format. A state department of corrections holds the sentence. A county jail lists who was booked last night, usually before any court has ruled. A statewide warrant system lists who is wanted, and the federal courts and federal custody sit apart from all of it. The criminal records API answers one HTTP request with records from whichever of those layers hold the person, each one in the same object and each one naming the jurisdiction it came from.

The envelope says what the answer is worth before you read a record. counts.sourcesOnFile is how many jurisdictions the index held for your scope; sourcesPending is how many are catalogued and not yet answering. An empty records[] on a complete answer is a clear result across the sources on file, nothing more and nothing less, which is the sentence a reviewer needs when a search finds nothing. Every field is defined in the criminal record object reference, and the response explained tutorial walks a real answer group by group.

FieldWhat it tells you
statuscomplete, or partial when a live source you named did not answer in time. A cached search is never partial.
counts.sourcesOnFile, sourcesPendingHow many jurisdictions the index held for this scope and how many are catalogued but not yet answering. This is the coverage behind the answer.
records[].recordTypeThe kind: jail_booking, doc_inmate, court_case or warrant. One object shape serves all four; the kind decides which blocks are filled.
records[].matchState, matchBasis, matchDetailWhy the record is in the list: dob_match, year_match, age_match or no_dob_age_year, the strategies that produced it, and a sentence a reviewer can read.
records[].dobVerification, unverifiedWhere the birth date agreement came from: the record itself, or a live source that confirmed it. A record with nothing to compare is kept and marked unverified.
records[].cases[].charges[]statute, description, severity, disposition and dispositionDate per charge. One case can hold a guilty felony and a dismissed misdemeanor side by side; read the charge, not the case.
records[].currentStatus, currentlyIncarceratedin_custody, released, on_probation, active_warrant and similar, plus two booleans so you never parse a status string.
records[].booking, sentence, parole, warrantThe kind-specific blocks: booking number and bond on a jail record, term and dates on a prison record, issuing agency on a warrant. Unused blocks are present and null.
records[].sources[]The jurisdiction code, its level (county, state, federal), the record link at the source, and whether this answer came from a live check.
records[].personRef, externalIdA stable person key across searches and the source’s own identifier, so a monitor or a later search recognises the same record.
usage, legal.noticeWhat a live check cost on this call, and the notice that the standard response is a public-records lookup, not a consumer report.

How a criminal records search works in three steps

Key, call, production. The request body is the one the sandbox documents for its felony test person, not a sketch.

01 · about 30 seconds

Mint a key

Sign up for a business account and create an os_test_ key in the dashboard. It answers against the public API for testing with synthetic people and is never billed.

02 · one request

Send a surname and a date of birth

query.lastName is required; a search without one is refused with 422 guard_unbounded_query rather than answered with a lottery. A first name and a full date of birth turn a common surname into a short, labelled list. Paging is page and perPage, 1 to 200.

03 · the same shape

Switch the key, keep the code

A production key (os_live_) answers the same path with the same envelope. Add query.state or query.county to scope a search, live to re-check named jurisdictions, and POST /v1/criminal/batch for up to 1,000 people in one call. The quickstart and every search parameter are in the docs.

cURL · the sandbox's felony scenario
curl -X POST "https://sandbox.offendersearch.app/v1/criminal/search" \
  -H "X-API-Key: $OFFENDERSEARCH_TEST_KEY" \
  -H "Content-Type: application/json" \
  -d '{
      "query": {
        "firstName": "Felony",
        "lastName": "Record",
        "dob": "1975-06-15"
      }
    }'

Python, Node and the response are in the hero above; the scenario menu switches to a custody record, a warrant and a clear answer. Postman and the OpenAPI spec: Postman collection · API reference.

Four criminal record kinds in one record object

Booking, custody, case and warrant. The sandbox's captured answer for each, so you can see which blocks a kind fills and which it leaves null.

jail_booking

Booking

County jail rosters

Who a county booked into custody, with the charges listed at booking, bond, the facility and usually a booking photo. A booking is an event, not an outcome: most carry no disposition at all, and many rosters publish an age rather than a birth date.

booking.bookingDatethe booking datebooking.bondamount and typecharges[].dispositionusually emptymugshotUrlwhere published
arrest records ›
doc_inmate

Custody

State prison systems

Who is serving a state sentence: facility, custody class, admission date, projected release, and the sentence and parole blocks where the department publishes them. A prison record is evidence of a conviction, and the conviction case usually rides along in cases[].

custodyFacilitythe unitreleaseDateprojectedsentence.minDate, maxDatethe termparole.eligibilityDatewhere published
inmate search API ›
court_case

Case

Court sources

A criminal case as the court publishes it: case number, court, filing date and status, with every charge carrying statute, severity, plea, disposition and date. The only kind that says how a matter ended, and the one with the narrowest coverage.

cases[].caseNumberthe docketcharges[].severityfelony · misdemeanorcharges[].dispositionas publishedcases[].sentencewhere stated
court records search ›
warrant

Warrant

Statewide warrant systems

An open warrant: the issuing agency, the issue date, the charge and currentStatus active_warrant. A warrant is an accusation that can be cleared at any time, which is why it is the record kind most worth a live re-check before anyone acts.

warrant.issuedBythe agencywarrant.issuedDatethe datecurrentStatusactive_warrantcharges[].descriptionthe charge
warrant search API ›
{
  "status": "complete",
  "counts": {
    "records": 1,
    "recordsReturned": 1,
    "sourcesQueried": 0,
    "sourcesComplete": 0,
    "sourcesIncomplete": 0,
    "candidatesCapped": false,
    "exclusionsIncluded": false,
    "sourcesOnFile": 1635,
    "sourcesPending": 330
  },
  "warnings": [],
  "page": 1,
  "perPage": 50,
  "totalPages": 1,
  "sourceStatus": [],
  "cappedOmittedSources": [],
  "omittedFields": [
    "sourceData"
  ],
  "proof": {
    "status": "none"

Four sandbox scenarios (Arrest Only, In Custody, Felony Record, Active Warrant), captured from the code the sandbox serves; the sample person’s empty keys are folded and the fold says so. Federal custody and federal court matters arrive in the same shape with sources[].level: federal; see federal criminal records. The county and state layers for non-developers: county criminal records · statewide criminal search · jail roster.

Live re-verification of a criminal record at its source

The index answers from what the jurisdictions have published; a live block asks a named jurisdiction again inside the request.

Add live.jurisdictions with the codes to re-check, US-DOC for federal custody or PA-WARRANT for a state warrant system, and those sources are queried during the call. Each one appears in sourceStatus with live: true, whether it answered, and when. A record a live source confirms for your date of birth is marked dobVerification: source_confirmed. Up to two live sources run inline; more than two answer 202 with a searchId to poll at GET /v1/criminal/searches/{searchId}.

The price is in the answer: usage.liveChargeUsd, at $0.02 per completed source with a $2.00 ceiling per search, and a source that did not answer is not charged. A search with live sources can come back partial; the records you received are real and the sources marked incomplete are unknown, so a partial answer is a lower bound and never a clear.

Documents follow the same searchId. POST /v1/criminal/report renders a verification PDF for $0.02: the query, the time, the records by match strength and each source citation, with X-Report-Id printed on it. On the registry side, live.evidence: "pdf" captures the registry’s own page behind a cover sheet with its SHA-256. An FCRA order’s report carries an Ed25519-signed receipt that anyone holding the file can check at /verify without uploading it. Providers who re-verify records before they go on a report should read the criminal record verification API page, and those ordering county searches the county criminal search API page; the reference is live evidence and live and async.

POST /v1/criminal/search · livesandbox scenario “Felony Record, US-DOC re-checked” · query {"firstName":"Felony","lastName":"Record","dob":"1975-06-15","live.jurisdictions":"US-DOC","live.evidence":"pdf"}
200 OK · the sandbox's answer, captured from its code
{
  "status": "complete",
  "counts": {
    "records": 1,
    "recordsReturned": 1,
    "sourcesQueried": 1,
    "sourcesComplete": 1,
    "sourcesIncomplete": 0,
    "candidatesCapped": false,
    "exclusionsIncluded": false,
    "sourcesOnFile": 1934,
    "sourcesPending": 197
  },
  "warnings": [],
  "page": 1,
  "perPage": 50,
  "totalPages": 1,
  "sourceStatus": [
    {
      "code": "US-DOC",
      "source": "US-DOC",
      "ok": true,
      "incomplete": false,
      "incompleteReason": null,
Read sourceStatus[0]: US-DOC, live: true, ok: true, zero records, and the time it answered. usage shows one live check billed. The sandbox returns proof.status: none; production attaches the document job when evidence is requested.Run it yourself with a test key ›

Criminal records API coverage by state and record kind

Jail rosters live against catalogued, and whether a statewide prison, court or warrant source answers today, from the live catalogue.

Depth differs by state, and that difference is the content of this table. A state can have a statewide warrant system and dozens of live jail rosters while its neighbour publishes neither and relies on a prison system alone. Court sources are the narrowest layer: 48 states have a statewide court source in the catalogue, and in the others a disposition is only reachable at the county court itself.

Build against the catalogue, not this page. GET /v1/criminal/sources needs no key and returns each jurisdiction with its kind and whether it is live; GET /v1/criminal/jurisdictions filters by state and record kind. Each state in the table links to its own criminal records page; the criminal records by state hub and the data sources catalogue list every source by name.

StateCounty jail rosters (live / catalogued)Prison systemCourtsWarrants
Alabama24 / 26StatewideStatewideStatewide
Alaska3 / 3StatewideStatewide—
Arizona16 / 23StatewideStatewide—
Arkansas31 / 34StatewideStatewideStatewide
California66 / 71StatewideStatewideStatewide
Colorado51 / 70StatewideStatewideStatewide
Connecticut0 / 1StatewideStatewideStatewide
Delaware6 / 6Statewide—Statewide
District of Columbia2 / 2StatewideStatewide—
Florida57 / 63StatewideStatewideStatewide
Georgia52 / 66StatewideStatewide—
Hawaii6 / 6StatewideStatewide—
Idaho38 / 50Statewide—Statewide
Illinois30 / 33StatewideStatewideStatewide
Indiana70 / 74StatewideStatewide—
Iowa22 / 22StatewideStatewideStatewide
Kansas18 / 21StatewideStatewideStatewide
Kentucky119 / 121StatewideStatewide—
Louisiana28 / 29StatewideStatewideStatewide
Maine21 / 21Statewide——
Maryland29 / 31StatewideStatewide—
Massachusetts19 / 20StatewideStatewide—
Michigan46 / 48StatewideStatewideStatewide
Minnesota30 / 31StatewideStatewideStatewide
Mississippi34 / 36StatewideStatewideStatewide
Missouri66 / 68StatewideStatewide—
Montana61 / 72StatewideStatewide—
Nebraska16 / 16StatewideStatewide—
Nevada17 / 24StatewideStatewideStatewide
New Hampshire13 / 13Statewide——
New Jersey25 / 26StatewideStatewideStatewide
New Mexico34 / 46StatewideStatewideStatewide
New York65 / 67StatewideStatewideStatewide
North Carolina39 / 40StatewideStatewideStatewide
North Dakota11 / 14StatewideStatewideStatewide
Ohio82 / 86StatewideStatewideStatewide
Oklahoma25 / 28StatewideStatewideStatewide
Oregon42 / 44StatewideStatewideStatewide
Pennsylvania69 / 71StatewideStatewideStatewide
Rhode Island0 / 1StatewideStatewideStatewide
South Carolina72 / 73StatewideStatewideStatewide
South Dakota21 / 22StatewideStatewideStatewide
Tennessee21 / 25StatewideStatewideStatewide
Texas84 / 104StatewideStatewideStatewide
Utah27 / 34StatewideStatewideStatewide
Vermont2 / 2StatewideStatewide—
Virginia60 / 62StatewideStatewideStatewide
Washington47 / 51StatewideStatewideStatewide
West Virginia11 / 11StatewideStatewideStatewide
Wisconsin29 / 33StatewideStatewide—
Wyoming16 / 29StatewideStatewide—
52 states and territories1,782 / 1,97954 systems48 states35 states

Jurisdictions in our catalogue as of 2026-11-08; a live jurisdiction answers a search today. Approximate, not an official figure. Exact, dated counts per jurisdiction: criminal coverage reference.

What the criminal records we index look like

Charge groups, felony share, convictions and photographs across the jail and court records in the index, weighted by state.

County jail records36 states · 12,884,134 records we index
Probation/parole violations and failure to appear16%of charges
Public order, trespass and property damage15%of charges
Drug possession14%of charges
Assault, battery and threats12%of charges
Traffic offenses (not DUI)11%of charges
DUI / DWI9%of charges
Theft, larceny and stolen property9%of charges
Domestic violence3%of charges
Burglary and breaking & entering1%of charges
Fraud, forgery and identity theft1%of charges
Weapons offenses1%of charges
Felony, where the charge level is stated54%4 states
Records with a photograph3%36 states
Court records36 states · 32,507,066 records we index
Traffic offenses (not DUI)14%of charges
Drug possession10%of charges
Public order, trespass and property damage9%of charges
Assault, battery and threats8%of charges
Theft, larceny and stolen property8%of charges
DUI / DWI5%of charges
Fraud, forgery and identity theft3%of charges
Probation/parole violations and failure to appear3%of charges
Domestic violence2%of charges
Weapons offenses2%of charges
Burglary and breaking & entering1%of charges
Drug sale, distribution or manufacture1%of charges
Sex offenses1%of charges
Felony, where the charge level is stated45%12 states
Convicted, where an outcome is stated29%23 states

Shares of the records we index for the place; approximate, not an official figure. A null cell was below the suppression floor. recentPct = records with a filed, offense or disposition date in the last 12 months, among dated records. Each national share is the mean of the state shares weighted by the records we index for that state; a charge group outside a state’s eight largest counts as zero there. As of 2026-11-03.

Jail records carry charges at booking and almost never an outcome, so the conviction share is a court-record figure only. Charge groups are our grouping of the text each court or jail publishes; the criminal charge types page explains the groups and what shows up on a background check puts them in context.

How criminal record matching and scoring work

Every record says why it is in the list, and a gap in the answer is said out loud.

01

The date of birth decides

dob_match is the only state that identifies a person. year_match and age_match are strong leads; no_dob_age_year means the record published nothing to compare, so it is kept, ranked lower and marked unverified. Only a contradicting date removes a record.

02

Confidence orders, matchState gates

matchConfidence is a ceiling on the evidence held, capped at 0.99, not a probability; a name-only hit on a common surname can score 0.80. Use the number to order a review queue and matchState to decide what runs automatically.

03

The charge, not the case

Dispositions are returned as the court published them, per charge, and an empty disposition stays empty. A booking or a warrant never reads as a conviction because its kind is on the record and its charges carry no outcome.

04

Incomplete is never clear

A live source that fails to answer is named in sourceStatus and the answer is partial. The deadline you set with deadlineMs bounds the wait, not the honesty of the result.

Criminal records API or FCRA criminal background check

Same records, two products. Which one your application needs depends on what the answer will decide.

Path 1

Data API, not FCRA

$0.15a call, 25 free, no card
  • 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.

Path 2

FCRA Partner Access

$4.95per order, searches and live checks included, no court fees
  • 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.

Criminal records API pricing per call

$0.15 a search covering every record kind in scope, $0.11 past 2,000 in a month. Live checks, monitors and the FCRA order are priced beside it.

ItemPriceUnit
Criminal search$0.15per call, the first 2,000 in a calendar month
Volume rate$0.11per call past 2,000 in a calendar month
Free to start25 callsonce per account, on production data, no card
Sandbox$060 calls a minute and 2,000 a day per test key
Live re-verification+$0.02per completed live source, $2.00 ceiling per search; a source that did not answer is not billed
Person monitor$3.00per person a month
FCRA order$4.95per 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.

Monthly calls:
$1,180
a month
$0.118
effective per call
8,000
calls at $0.11

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.

Worked examples by volume: background check API pricing · every rate: pricing.

Three ways developers use the criminal records API

Each one reads a different part of the answer.

Onboarding

Gate a sign-up on matchState

A marketplace runs one search at sign-up and acts automatically only on dob_match; everything weaker lands in a review queue with sources[].recordUrl open beside it. The workforce screening API page covers the re-screen and the FCRA step for gig and staffing platforms.

Re-screening

Run the roster through batch

POST /v1/criminal/batch takes a JSON list or CSV of up to 1,000 people and returns results[] in input order, one envelope per row, each billed as one call. The bulk criminal record search page shows the dashboard version of the same job.

Monitoring

Watch for a new record

POST /v1/monitors with product: criminal keeps a standing watch on a person for $3.00 a month and delivers new, changed and removed events by HMAC-signed webhook. Details on the continuous criminal monitoring API page and in monitoring.

Criminal records API compared with published screening prices

A per-call records API beside a per-report screening service and a per-credit data vendor, from their public pages on the dates shown. Rows where another vendor does more are marked.

AspectCheckrSearchBugOffenderSearch criminal records API
What you pay forA finished consumer report, per report, by package; court and database fees passed through at costPrepaid balance of $10 to $5,000, charged per successful query; Criminal Check priced per searchOne 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
County courthouse searchwhere another vendor does moreIncluded in Essential ($59.99); as an add-on $25 a check, plus pass-through feesNot stated on its public pagesNo courthouse pulls. Statewide court sources in 48 states, plus live re-verification of named jurisdictions at +$0.02 a source
Free tierwhere another vendor does moreNo free trial listed on its pricing page; a staging environment with mocked data is available on requestA sandbox test account with "a limited number of live queries"; the number is not stated25 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 moreA 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 queryA clear answer is a billed call: the response says which sources answered, which is the evidence a clear needs
Test environmenta staging environment with mocked data, available once Checkr grants access (api.checkr-staging.com)Sandbox API test account on requestSelf-serve sandbox with documented test people; mint an os_test_ key in the dashboard
Rate limit1,200 requests a minute across all endpoints; 429 with X-Ratelimit-Limit, -Remaining and -Reset headersNot stated on its public pagesNo published per-key ceiling in production; a 429 with Retry-After only at capacity, never billed
Webhookswebhooks signed with HMAC-SHA256 in an X-Checkr-Signature header; retries every minute for 10 minutes, then every hour for 24 hoursNot stated on its public pagesAsync 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
FCRA consumer reportsYes: every report is a consumer report, $29.99 to $94.99 by packageNot stated on its public pagesThrough FCRA Partner Access: $4.95 an order, searches and live checks included, no court fees
Continuous monitoringCheckr offers continuous criminal search at $1.70 per individual a month and continuous MVR at $2.50 per driver a monthNot stated on its public pages$3.00 a month per person, $10.00 per location, alerts by signed webhook

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 criminal records API

Reference, test tooling and clients.

Test

Criminal sandbox with its scenario table · Postman collection with sandbox bodies pre-filled · webhook tester for a signed sample event.

Agents

The MCP server exposes registry and criminal lookups as tools for Claude, Cursor and other agents; the MCP server tutorial reads one agent run against the sandbox.

Clients

Python and Node clients publish with the first registry release; until then the REST examples above are the integration. Status and the method surface: SDKs: Python, Node, CLI · background check API in Python · background check API in Node.js.

Criminal records API limits and what it leaves out

Rate limits, the 4,000-record response cap, the 429 body, and the records this API does not return.

LimitValue
Sandbox, per test key60 calls a minute, 2,000 a day; nothing billed
Production, per keyNo published ceiling. A 429 only when the service is at capacity, with Retry-After; a 429 is never billed
Records per responseUp to 4,000 in one answer; above that capped: true, and perPage pages through the rest
Batch1,000 rows a call; a failing row is reported in place and never stops the batch
DeadlinedeadlineMs bounds the wait for slow jurisdictions; an unanswered one is named in sourceStatus and the answer says partial
EndpointsPOST /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 fingerprint or identity-number search. Matching is on name, date of birth and the identifiers a source publishes; there is no lookup by inmate or case number, though externalId lets you recognise a record you have seen.
  • Federal custody is re-checked only on request. Name US-DOC in live.jurisdictions; the index alone does not call it.

Retry rules and backoff: rate limits, retries and idempotency · every status code: errors.

What a rate-limit answer looks like
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.

Criminal records API questions

Billing, the sandbox, retention, scoping, corrections and what a search includes.

When is a criminal records API call billed?

On a 200 answer, whether or not it holds records: the answer names the jurisdictions that were on file for your scope, which is what a clear result needs. A 429 or a 4xx is never billed. Each row of POST /v1/criminal/batch is one call, and a row that fails validation is reported in place and not charged. A live source is billed only when it completes.

What does the sandbox allow before I buy anything?

A test key (os_test_) answers 60 calls a minute and 2,000 a day with documented synthetic people, in the production shape, and bills nothing. It also renders the verification PDF for its sample records. Your first 25 production calls are free as well, with no card.

How long can I come back for a search result or its PDF?

Keep the searchId. It is the input to POST /v1/criminal/report, which renders the verification PDF for $0.02 within 7 days of the search without running it again, and it is what a monitor alert or a later dispute cites.

Does a jail roster that publishes only an age ever produce a dob_match?

Not from the index. The record keeps the age and the date it was stated, dobPrecision says age, and the match is labelled age_match. On a live search with a full date of birth, a source that returns the person for that date sets dobVerification: source_confirmed; that is the one way an age-only record is confirmed.

Can I limit a search to one state or one county?

Yes. query.state and query.county scope the search, and the answer’s coverage.scope echoes what was applied with the sources on file for it. GET /v1/criminal/jurisdictions?state=TX&recordKind=jail-roster lists what a scope will reach before you send it.

What happens to records about a person who is later cleared or released?

The record stays and the status moves. A released person reads currentlyIncarcerated: false with everIncarcerated: true; a record the source stops listing keeps its last state and is flagged in lifecycle. A person monitor reports the change as a changed or removed event rather than making you poll.

How is a wrong or outdated criminal record corrected?

The record belongs to the jurisdiction in sources[].recordUrl, and a correction has to happen there; a live re-check then shows the current state. Under FCRA Partner Access the dispute endpoint runs that re-check for the consumer, with an outcome inside 30 days and a correction sent to every partner that received the record.

Are exclusion lists and registry records part of a criminal search?

Conviction-based healthcare exclusions arrive by default as recordType: healthcare_exclusion; administrative exclusions need include: ["exclusions"]. Statewide registry sources in the criminal catalogue ride along, and the full 58-registry search is POST /v1/search on the same key, described on the sex offender API page.

Criminal records API how-to guides

Runnable tutorials that use this endpoint as the worked example, each against the sandbox.

Criminal records by name and date of birth ›Why the date of birth decides whether a hit is an identification or a lead.
Court records API tutorial ›Cases, charges and dispositions, and how to read a case that holds both a conviction and a dismissal.
Arrest records API example ›A jail booking as JSON, why a booking is not a conviction, and a monitor for a new one.
Build an inmate search tool ›Custody status, facility and release dates from the criminal records API.
Bulk background checks from a CSV ›The batch endpoint, 1,000 rows a call, results in input order, billed per row.
Monitor a person with webhooks ›A standing watch on a person, signed alerts, and the receiver that verifies them.
No-match and multiple-match results ›The three shapes of "nothing", possibles, and a decision table per matchState.
Background check API response explained ›Every field of a real sandbox response, group by group.
Rate limits, retries and idempotency ›429 semantics, backoff that honours Retry-After, and why a repeated POST is a second search.
Test a background check integration ›The sandbox scenario matrix, a test suite, CI and the switch to production.
API errors ›HTTP status first, a machine code, a message you can act on — and our catalogue.
Webhook example ›Receive, verify the signature and retry, in 40 lines of Express or FastAPI.

All guides: Learn APIs by example · reference: developer docs · packages: SDKs and CLI.

Related criminal records API pages

The rest of the developer surface, one anchor per page.

Background check API ›Criminal records and 58 US sex offender registries on one key, per call.
Sex offender API ›One POST across 58 US registries, scored and cited.
Free background check API ›25 free calls on real data, no card, plus the free sandbox.
Employment screening API ›The public-records stage of a hiring pipeline, and the FCRA path for the decision.
Tenant screening API ›The registry and criminal layer behind a rental application.
Inmate search API ›State prison and county jail custody records.
Background check API pricing ›Costs from 100 to 100,000 searches a month.
Public API for testing ›A free sandbox with documented test people in the production shape.
SDKs: Python, Node, CLI ›Client status and the method surface, one per endpoint.
Postman collection ›Every endpoint with sandbox bodies pre-filled.
MCP server ›Registry and criminal lookups as tools for Claude, Cursor and agents.
API documentation ›Reference, guides and the OpenAPI spec.

Run your first criminal records search

25 calls free, no card, the same key as the registry search. The sandbox answers in the production shape while you build.