OffenderSearch
Background check API · pay per call

A background check API for criminal records and registries.

One POST returns scored JSON from more than 1,900 live county, state and federal jurisdictions and 58 US sex offender registries; a key works in about a minute, a call is $0.15, and the first 25 are free with no card.

Get a free API key25 free calls · no cardRead the docs

The umbrella page for the OffenderSearch APIs. Each endpoint has its own page: the criminal records API for jail, prison, court and warrant records, the sex offender API for the registries, and the free background check API for the trial.

POST /v1/search · POST /v1/criminal/search · sandbox
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"
      }
    }'
One strong match: DOB-verified (matchState dob_match), high confidence, photo, offense, registry state and two addresses.Sandbox people are synthetic; production answers have the same shape.
58US sex offender registries, one POST
1,934live criminal jurisdictions, by state, as of 2026-11-08
25free calls to start, no card
$0.15per call, $0.11 after 2,000 in a month, pricing

Updated November 8, 2026 · API changelog

What a background check API call returns

The sandbox's own answers, captured from the code that serves it: a registry hit, a criminal court hit and a clear, each shown whole.

POST /v1/search · hitExact match, date of birth verified · query {"firstName":"Exact","lastName":"Match","dob":"1980-01-01"} · 200 lines
{
  "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
    }
  ]
}
One record from the Ohio registry; all 58 registries answered. The capture folds identical “matched 0” rows and says so inline.Run it with a test key ›
POST /v1/criminal/search · hitFelony conviction · query {"firstName":"Felony","lastName":"Record","dob":"1975-06-15"} · 172 lines
{
  "status": "complete",
  "counts": {
    "records": 1,
    "recordsReturned": 1,
    "sourcesQueried": 0,
    "sourcesComplete": 0,
    "sourcesIncomplete": 0,
    "candidatesCapped": false,
    "exclusionsIncluded": false,
    "sourcesOnFile": 1567,
    "sourcesPending": 347
  },
  "warnings": [],
  "page": 1,
  "perPage": 50,
  "totalPages": 1,
  "sourceStatus": [],
  "cappedOmittedSources": [],
  "omittedFields": [
    "sourceData"
  ],
  "legal": {
    "notice": "Not a consumer report. This information may not be used for any purpose under the Fair Credit Reporting Act (15 U.S.C. § 1681 et seq.)."
  },
  "searchId": "srch_sbx_cr_felony",
  "meterEvents": [],
  "sandbox": true,
  "records": [
    {
      "recordType": "court_case",
      "externalId": "SBX-CR-2015-000123",
      "personRef": "prs_6e1aaefd188032a7e6eb",
      "name": {
        "first": "Felony",
        "middle": "Sample",
        "last": "Record",
        "suffix": ""
      },
      "aliases": [],
      "dob": {
        "date": "1975-06-15",
        "birthYear": 1975,
        "birthMonth": 6,
        "age": null,
        "ageAsOf": null,
        "dobPrecision": "full"
      },
      "birthYear": 1975,
      "dobPrecision": "full",
      "sex": "M",
      "race": "White",
      "state": "OH",
      "county": "Sample",
      "currentStatus": "on_probation",
      "currentlyIncarcerated": false,
      "everIncarcerated": true,
      "priorFelony": false,
      "matchConfidence": 0.99,
      "matchState": "dob_match",
      "dobVerification": "record",
      "unverified": false,
      "matchBasis": "lastName:exact firstName:exact dob:match",
      "matchDetail": "name and full date of birth agree",
      "cases": [
        {
          "caseNumber": "SBX-CR-2015-000123",
          "court": "Sample County Court of Common Pleas",
          "county": "Sample",
          "state": "OH",
          "level": "county",
          "filedDate": "2015-03-02",
          "status": "Closed",
          "charges": [
            {
              "statute": "SAMPLE 2911.12",
              "description": "Burglary",
              "severity": "felony",
              "disposition": "Guilty",
              "dispositionDate": "2015-09-14",
              "offenseDate": "2015-02-20",
              "plea": "Guilty",
              "counts": 1
            },
            {
              "statute": "SAMPLE 2913.02",
              "description": "Theft",
              "severity": "misdemeanor",
              "disposition": "Dismissed",
              "dispositionDate": "2015-09-14",
              "offenseDate": "2015-02-20",
              "plea": "",
              "counts": 1
            }
          ],
          "caseType": "FELONY",
          "judge": "Hon. Sample Judge",
          "attorney": "Sample Defender",
          "prosecutor": "Sample County Prosecutor",
          "division": "General Division",
          "nextHearing": {
            "date": null,
            "time": null,
            "type": null,
            "courtroom": null
          },
          "events": [
            {
              "date": "2015-03-02",
              "type": "ARRAIGNMENT",
              "description": null,
              "outcome": "Plea of not guilty entered"
            },
            {
              "date": "2015-09-14",
              "type": "PLEA HEARING",
              "description": null,
              "outcome": "Guilty plea to count 1; count 2 dismissed"
            }
          ],
          "sentence": {
            "length": "3 years",
            "minDate": "2015-09-14",
            "maxDate": "2018-09-14",
            "probation": "2 years community control",
            "fine": 500.0,
            "dischargeDate": null,
            "years": 3,
            "months": null,
            "goodTimeLaw": "",
            "truthInSentencing": ""
          }
        }
      ],
      "sentence": null,
      "sources": [
        {
          "code": "OH-SAMPLE",
          "level": "county",
          "recordUrl": "https://offendersearch.app/docs/sandbox",
          "lastCheckedAt": "2026-10-01T00:00:00+00:00",
          "live": false
        }
      ],
      "lifecycle": {
        "firstSeen": "2025-01-10T00:00:00+00:00",
        "lastSeen": "2026-10-01T00:00:00+00:00",
        "presentInLastSweep": true,
        "droppedOut": false,
        "droppedOutDetected": null,
        "dropInterpretation": "unknown",
        "sourceLastUpdated": null
      },
      "physical": {
        "height": "5'10\"",
        "weight": "180 lbs",
        "hairColor": "Brown",
        "eyeColor": "Blue",
        "build": "Medium",
        "marks": "Tattoo, left forearm (sample)",
        "heightInches": 70,
        "weightPounds": 180
      },
      "identifiers": {
        "stateId": "OH00012345",
        "fbiNumber": "123456AB7"
      },
      "recordCategory": "court"
      /* … 31 more keys, always present ("" / null / [] when the source publishes nothing) */
    }
  ]
}
A court case with two charges, one guilty plea and one dismissal, and the sentence; empty keys are named in a fold.Run it with a test key ›
POST /v1/search · clearClear visitor · query {"firstName":"Clear","lastName":"Visitor"} · 39 lines
{
  "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": []
}
Zero records, zero incomplete sources. The empty array is an answer only because the counts say the search finished.Run it with a test key ›

Both endpoints share one envelope and one scoring model, so code that reads a registry record reads a criminal record too. These are the fields a decision depends on; the registry record and criminal record references define the rest.

FieldWhat it tells you
status · countsRead these first. sourcesIncomplete above zero means a jurisdiction did not answer, and the search is not a clear.
matchStateHow the person matched: dob_match, year_match, age_match, dob_near_match or no_dob_age_year.
matchBasis · matchDetailWhich identifiers agreed and by which strategy, so a reviewer sees why the record is here.
matchConfidence · unverifiedA score to threshold on, and a flag that is true whenever the date of birth did not confirm the match.
recordTypeRegistry records say sex_offender; criminal records say court_case, jail_booking, doc_inmate or warrant.
cases[].charges[]Statute, description, severity, plea and disposition per charge, on court records. A booking carries charges with no disposition.
sources[]The jurisdiction that holds the record, its recordUrl, and whether this answer was re-verified live.
personRefA stable reference for the same person across searches; the thing a monitor watches.

Field by field: background check API response explained · the shapes of “nothing”: no-match and multiple-match results.

How a background check API search works, in three steps

Timed from a blank account. Only the key changes between the sandbox and production.

01
Create a keyAbout 30 seconds

Sign up and create a key in the dashboard. A live key works at once on the 25-call trial with no card; an os_test_ key routes to the sandbox and is never billed. Keep it server-side, in X-API-Key.

02
Send one POSTUnder a minute

POST /v1/search for the registries, POST /v1/criminal/search for criminal records, one body shape for both. A first and last name is the minimum; a full date of birth turns a hit into an identification. The cURL beside this is the sandbox’s felony scenario, runnable as written.

03
Go liveAn afternoon

Swap the test key for a live key; the request and response do not change. Production work is the matching rule you automate on, a webhookUrl for long searches, POST /v1/batch for up to 1,000 rows, and a monitor for the people you keep. The tutorial walks the path on the sandbox.

Background check API in Python · background check API in Node.js · quickstart.

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"
      }
    }'

Background check API coverage by state

Each row comes from the catalogue the API itself publishes. A live jurisdiction answers a search today; a catalogued one is on the roster.

County jail rosters are the deepest layer and the most uneven; prison, court and warrant systems are statewide where a state publishes them; the registry column is the 58-registry roster. Custody questions have the inmate search API; statewide warrant systems have the warrant search API.

StateCounty jail rosters (live / catalogued)Prison systemCourtsWarrantsRegistry
Alabama24 / 26StatewideStatewideStatewideAlabama registry
Alaska3 / 3StatewideStatewide—Alaska registry
Arizona16 / 23StatewideStatewide—Arizona registry
Arkansas31 / 34StatewideStatewideStatewideArkansas registry
California66 / 71StatewideStatewideStatewideCalifornia registry
Colorado51 / 70StatewideStatewideStatewideColorado registry
Connecticut0 / 1StatewideStatewideStatewideConnecticut registry
Delaware6 / 6Statewide—StatewideDelaware registry
District of Columbia2 / 2StatewideStatewide—District of Columbia registry
Florida57 / 63StatewideStatewideStatewideFlorida registry
Georgia52 / 66StatewideStatewide—Georgia registry
Hawaii6 / 6StatewideStatewide—Hawaii registry
Idaho38 / 50Statewide—StatewideIdaho registry
Illinois30 / 33StatewideStatewideStatewideIllinois registry
Indiana70 / 74StatewideStatewide—Indiana registry
Iowa22 / 22StatewideStatewideStatewideIowa registry
Kansas18 / 21StatewideStatewideStatewideKansas registry
Kentucky119 / 121StatewideStatewide—Kentucky registry
Louisiana28 / 29StatewideStatewideStatewideLouisiana registry
Maine21 / 21Statewide——Maine registry
Maryland29 / 31StatewideStatewide—Maryland registry
Massachusetts19 / 20StatewideStatewide—Massachusetts registry
Michigan46 / 48StatewideStatewideStatewideMichigan registry
Minnesota30 / 31StatewideStatewideStatewideMinnesota registry
Mississippi34 / 36StatewideStatewideStatewideMississippi registry
Missouri66 / 68StatewideStatewide—Missouri registry
Montana61 / 72StatewideStatewide—Montana registry
Nebraska16 / 16StatewideStatewide—Nebraska registry
Nevada17 / 24StatewideStatewideStatewideNevada registry
New Hampshire13 / 13Statewide——New Hampshire registry
New Jersey25 / 26StatewideStatewideStatewideNew Jersey registry
New Mexico34 / 46StatewideStatewideStatewideNew Mexico registry
New York65 / 67StatewideStatewideStatewideNew York registry
North Carolina39 / 40StatewideStatewideStatewideNorth Carolina registry
North Dakota11 / 14StatewideStatewideStatewideNorth Dakota registry
Ohio82 / 86StatewideStatewideStatewideOhio registry
Oklahoma25 / 28StatewideStatewideStatewideOklahoma registry
Oregon42 / 44StatewideStatewideStatewideOregon registry
Pennsylvania69 / 71StatewideStatewideStatewidePennsylvania registry
Rhode Island0 / 1StatewideStatewideStatewideRhode Island registry
South Carolina72 / 73StatewideStatewideStatewideSouth Carolina registry
South Dakota21 / 22StatewideStatewideStatewideSouth Dakota registry
Tennessee21 / 25StatewideStatewideStatewideTennessee registry
Texas84 / 104StatewideStatewideStatewideTexas registry
Utah27 / 34StatewideStatewideStatewideUtah registry
Vermont2 / 2StatewideStatewide—Vermont registry
Virginia60 / 62StatewideStatewideStatewideVirginia registry
Washington47 / 51StatewideStatewideStatewideWashington registry
West Virginia11 / 11StatewideStatewideStatewideWest Virginia registry
Wisconsin29 / 33StatewideStatewide—Wisconsin registry
Wyoming16 / 29StatewideStatewide—Wyoming registry
52 states and territories1,782 / 1,97954 systems48 states35 states58 registries

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.

Build against GET /v1/criminal/sources rather than this table: it returns the same roster with each jurisdiction’s scope. What is and is not returned beyond criminal and registry data is on the public records API page.

What the criminal records behind the API look like

Weighted shares across the records we index: what a hit usually is, before you design the review queue.

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
Female, where sex is stated25%32 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.

A jail booking is arrest-stage: charges as filed, no disposition, often a photograph and a custody status. A court case carries what happened: plea, disposition per charge, sentence. Each record is typed so your rules can treat a conviction differently from a booking; the criminal records API page shows one captured record of each kind.

Severity and disposition are present only where the source states them; treat a blank as unknown. Worked example: the court records tutorial.

Matching and accuracy in a background check API

Public records are filed under names. The API says how well a record matched, and never calls a half-finished search clear.

matchName rulesUse
strictExact first and last name onlyFewest false positives; pair it with a date of birth
balancedNicknames, initials, middle names and one-letter typos on the first name; exact last nameThe default
broadTwo-letter typos on the first name; prefix and typo tolerance on the last nameMost recall; expect low-confidence rows to triage

Pick the mode per request: a queue with a reviewer can run broad and triage; an automated gate runs strict or balanced with a full date of birth and acts only on dob_match. The matching reference lists each strategy the basis string can name.

The exact-DOB rule. A record whose published birth date agrees with yours is dob_match, the only state to automate on. A birth-year or age match is a review item; a name-only record is a lead. A record whose birth date contradicts yours is dropped, unless dobTolerance says the difference looks like a typo, in which case it comes back flagged.

Incomplete is never clear. A jurisdiction that did not answer in time is named in sourceStatus with a reason, counts.sourcesIncomplete goes above zero, and the response says partial. Treat that as “not yet”: wait on the searchId or re-run. An empty records array alone is not an answer.

No accuracy percentage. We do not publish a measured match-accuracy figure, because none exists that we would stand behind. The API gives you the evidence per record instead, matchBasis and matchConfidence, so you can measure it on your own traffic and set your own thresholds.

Two paths: data API and FCRA background check orders

Same records, different process. The question is whether the result will decide a hire, a home, credit or insurance.

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.

Hiring flows read the employment screening API; rental flows the tenant screening API. Screening companies that need a record confirmed at its source before it goes on a report use the criminal record verification API.

Background check API pricing, per call

One table, one unit column. Every figure here is the constant the billing code reads.

ItemPriceUnit
Registry or 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
Location monitor$10.00per location a month
FCRA order$4.95per order; sex offender and criminal court search included, with no court fees or extra charges
Map API$300monthly minimum, Map API only, applied toward Map API usage

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.

A clear is a billed call, because the response that says which 58 registries answered is the evidence a clear needs. No per-state fee, no charge for photographs, scoring or radius search, no pass-through court fee on a name search. Monthly examples, overage, taxes and refunds: background check API pricing.

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

Security and trust in the background check API

Only what is in place today; no certification we do not hold.

In transit and at rest

All traffic is served over TLS; stored results and reports are encrypted at rest with AES-256. API keys are stored hashed, one per environment, revocable on their own.

Retention you can plan around

Stored results resolve by searchId for 14 days; a verification PDF can be requested for 7 days. After that, the citations you kept with the decision are the record.

Signed webhooks

Each event carries X-Offendersearch-Signature: a timestamp and an HMAC-SHA256 over t.body with your endpoint secret. The webhook tester shows a real signed event and checks it in the browser.

Receipts anyone can check

An FCRA report PDF carries an Ed25519-signed receipt with the file’s hash and a QR code to /verify, where anyone holding the file confirms it without uploading it. Live re-verification can return an evidence PDF per source.

HIPAA and a BAA for enterprise

Care providers handling patient or applicant data under HIPAA sign a BAA before the first search; the HIPAA page lists the controls. Subprocessors and residency: talk to sales.

A dispute path with a clock

On an FCRA order a dispute, opened by you or by the consumer, starts a reinvestigation with the authority that holds the record on a 30-day clock, and the correction reaches each partner that received it.

Three background check API use cases, one field each

The same endpoints serve all three; one field or call differs.

Admissions and visitor screening

counts.sourcesIncomplete

A referral or front desk screens a name against the registries before a bed is offered or a visit begins; no hiring or housing decision is involved, so the data API fits. The field that matters says whether the search finished: a clear with sourcesIncomplete: 0 is a clear, and anything else is “not yet”.

See the sex offender API · healthcare exclusion check API.

Gig marketplace onboarding, then a monitor

alert.eventType

One criminal search when a provider joins, POST /v1/batch for the periodic re-screen, and POST /v1/monitors on the personRef for anyone who stays. The monitor’s webhook adds a field a search never has, eventType: new, changed or removed, so the trust team acts on a change instead of re-reading a result. $3.00 a person a month.

See the workforce screening API · continuous criminal monitoring API.

Tenant screening through the FCRA path

permissiblePurpose

A rental decision is a consumer-report use, so the same key places an FCRA order instead of a search. The request carries a field the data API does not accept, permissiblePurpose, with the applicant’s consent beside it; the order runs the notices, the consumer’s copy and the dispute window on one id, for $4.95.

See the tenant screening API · FCRA orders API.

How this background check API compares with Checkr and SearchBug

From each vendor's own published pages, with the read date. The rows where another vendor does more are kept.

AspectCheckrSearchBugOffenderSearch 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.

A report-ordering API returns a finished consumer report per report; a data API returns the records in the same HTTP response, per call, and leaves the decision to you. The Checkr API alternative page maps the objects field by field.

Developer resources for the background check API

Everything a first integration reaches for, in one place.

OpenAPI 3 specification ›The contract the reference pages are checked against; generate a typed client from it.
Postman collection ›Each endpoint with sandbox bodies pre-filled and an environment for the test key.
MCP server ›Registry and criminal lookups as tools for Claude, Cursor and other agents, on your key.
llms.txt ›A plain-text map of the docs for models and agents.
API changelog ›Dated entries for each field, endpoint and behaviour change.
Sandbox ›Documented synthetic people; 60 calls a minute and 2,000 a day per test key.
Webhook tester ›A hosted endpoint that receives a signed event and verifies it in front of you.
SDKs: Python, Node, CLI ›Typed clients that publish to PyPI and npm with the first registry release; until then, the REST examples above are the integration.

Background check API limits and what it does not return

Rate limits, the 4,000-record response cap, one real error body, and the scope line.

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/search and /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.

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.

Background check API FAQ

Billing timing, retention, the sandbox, webhooks, state rules and disputes: the questions the sections above do not answer.

When is a call billed, and when is it not?

A completed search is one call whether it finds records or not; a registry search and a criminal search are two calls; a batch row is one. A 429, a 422 and a batch row that errors are not billed. After the 25 free calls you add a card and are charged at the end of each calendar month, at $0.15 and then $0.11 after call 2,000.

What does the sandbox return, and what are its limits?

Documented synthetic people in the production shape: a date-of-birth-verified hit, a name-only hit, an alias match, a felony case, a booking without a disposition, an active warrant, a person in custody, and clears. An os_test_ key allows 60 calls a minute and 2,000 a day, bills nothing; an account can hold 3 at once.

How long are results kept, and what should I store?

A searchId resolves to its stored results for 14 days; a verification PDF can be requested for 7 days. Keep the record identifiers, matchBasis and sources[].recordUrl with your decision; that is what a later review asks for.

How do I verify a webhook came from you?

Read X-Offendersearch-Signature: t= is unix seconds, v1= is hex. Compute HMAC-SHA256 with your endpoint secret over t, a dot and the raw body; compare in constant time and reject a stale timestamp. Receivers in Express and FastAPI: the webhook example.

Can I search without a date of birth?

Yes. Records come back as no_dob_age_year with unverified: true: a lead for a person, not an identification. dobTolerance of 1 or 2 keeps records whose birth date looks like a typo of yours, flagged dob_near_match; query.state narrows to one state.

What does "live" mean on this page?

Two things. A live jurisdiction answers a search today; the coverage table counts those. Live re-verification is a request option: a live block names jurisdictions to re-check at query time, +$0.02 per source that answers, $2.00 ceiling per search, with an evidence PDF per source on request. A source that does not answer is not billed.

Do state rules limit what I can do with registry records?

Some states restrict the use of their registry information in employment or housing decisions, and a few forbid it. On an FCRA order those rules are applied before a record is furnished, by the use location you send; the FCRA docs list them with citations. On the data API those decisions are out of scope.

How is a record disputed, and how fast?

On an FCRA order you call the dispute endpoint, or the consumer uses the portal; a reinvestigation opens with the authority that holds the record on a 30-day clock, and the outcome arrives by webhook. On the data API there is no consumer file; the recordUrl lets a reviewer check the source, and support takes reports of a record that no longer appears there.

Learn the background check API by example

Runnable tutorials, each one against the sandbox.

Background check API tutorial ›A first registry and criminal check in ten minutes, on the sandbox, in curl, Python and Node.
Background check API response explained ›Every field of a real sandbox response, group by group.
Criminal records by name and date of birth ›Why the date of birth decides whether a hit is an identification or a lead.
No-match and multiple-match results ›The three shapes of "nothing", possibles, and a decision table per matchState.
Test a background check integration ›The sandbox scenario matrix, a test suite, CI and the switch to production.
Monitor a person with webhooks ›A standing watch on a person, signed alerts, and the receiver that verifies them.

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

Related background check API pages

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

Criminal records API ›Court cases, jail bookings, prison custody and warrants as JSON.
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.

Get a free background check API key

25 calls on production data, no card, no sales call. The first request works in about a minute.