Regulated County Checks provide county-level or statewide criminal background check results for a specific jurisdiction. county_fips_code is required. Provide a 5-digit FIPS code for a county-level search, or the literal statewide for a state-level search. Results include checks at the record, case, and charge levels indicating compliance with applicable legal rules. A permissible purpose is required for FCRA compliance.
Create a new regulated county criminal check for a specific jurisdiction.
This endpoint initiates a county-level or statewide criminal background check using either provided PII (personally identifiable information) or an existing profile. Results include legal annotation checks at the record, case, and charge levels indicating whether items should be included, investigated, or removed based on applicable regulations.
A permissible purpose must be provided to comply with FCRA requirements.
county_fips_code is required along with the state: provide a 5-digit FIPS code for a county-level check, or the literal statewide for a state-level check.
Profile vs inline PII: Submit either a profile_id or inline PII/address fields—not both. Combining profile_id with name fields, addresses, or other PII returns 400 Bad Request. reference_id may be sent alongside profile_id. Empty addresses: [] counts as a supplied address parameter and cannot be paired with profile_id.
Required fields when providing PII (without profile_id):
- first_name
- last_name
- dob
- state
- county_fips_code
- filter_context
- permissible_purpose
When using a profile_id, state, county_fips_code, filter_context, and permissible_purpose are required.
Request optional response fields. Repeat the parameter for multiple values.
| Items Enum Value | Description |
|---|---|
| profile | Embeds the full profile object in place of |
| review | Embeds the regulated check review object (accept/decline/dispute status). |
The request body for creating a regulated county check
Request to create a regulated county check using personally identifiable information (PII). Set county_fips_code to the literal statewide to perform a state-level search instead of a county-level search. A permissible purpose must be provided to comply with FCRA requirements.
Set to true to declare that the subject does not have a middle name.
Mutually exclusive with a non-empty middle_name: the API rejects requests that supply both a present middle_name and no_middle_name: true. An empty or null middle_name with no_middle_name: true is allowed. A non-empty middle_name may be supplied with no_middle_name: false.
Allowed with full_name: full_name and no_middle_name may be sent together. That is not the same as supplying middle_name — when the flag is true, parsing stores only a first name and surname, and any token the parser would have treated as a middle name is folded into the last name (for example full_name: "John Quincy Doe" becomes first name John and last name Quincy Doe, with middle_name empty).
Setting this to true clears a middle name already stored on a referenced profile. Supplying a non-empty middle_name without this field sets no_middle_name to false. When true, products that perform criminal-record identity matching exclude records with a middle name, narrowing matches to subjects with no middle name on record. When supplied with profile_id, the value is persisted to the referenced profile (same account-scoped profile the check is created against). Leave as false (or omit) if unsure.
Either send the full name, or first, middle (optional), and last names, but not both. If you send a full name, we will attempt to parse it into first name, middle name(s) and last name. With no_middle_name: true, any parsed middle token is folded into the last name instead of being stored as a middle name.
Date of birth in the form YYYYMMDD. Must be a valid date and cannot be in the future. If invalid, the API returns a 400 with a validation_error pointing to /dob.
The two-letter US state code for the search jurisdiction.
Use a 5-digit county FIPS code for a county-level criminal search. Use the literal statewide for a state-level criminal search covering the jurisdiction identified by state (the API accepts statewide case-insensitively and normalizes it to lowercase in stored search criteria).
Context information used to determine which legal rules apply when filtering check results. Jurisdictions help identify applicable state and local regulations that may affect which records can be reported.
{ "candidate_jurisdiction": { "state": "CA" }, "decider_jurisdiction": { "state": "NY" } }
The permissible purpose for requesting this criminal record check, as required by the Fair Credit Reporting Act (FCRA). This must be provided for all regulated instant criminal checks to ensure compliance with federal regulations.
A reference identifier for linking related records. Limited to 64 alphanumeric characters, underscores, and hyphens.
Primary address for the candidate. Used during result processing for identity matching and ROSIE scoring. Prefer addresses for new integrations; when both are provided, address is treated as the primary entry.
On inline create (without profile_id), optional address or addresses[] are saved to the new profile.
Optional addresses associated with the candidate. Used during result processing for identity matching and ROSIE scoring. Index 0 is the primary address.
On inline create, addresses are saved to the new profile.
- Checkr Trust APIhttps://api.checkrtrust.com/v1/regulated/county_checks
curl -i -X POST \
'https://api.checkrtrust.com/v1/regulated/county_checks?include%5B%5D=profile' \
-H 'Authorization: Bearer <YOUR_TOKEN_HERE>' \
-H 'Content-Type: application/json' \
-d '{
"first_name": "Jane",
"middle_name": "Mary",
"last_name": "Smith",
"dob": "19900115",
"state": "CA",
"county_fips_code": "06075",
"filter_context": {
"candidate_jurisdiction": {
"state": "CA"
},
"decider_jurisdiction": {
"state": "NY"
}
},
"permissible_purpose": "Employment"
}'Created
A regulated county criminal check response.
A universally unique identifier (UUID) in standard format.
An ISO 8601 formatted date-time string.
An ISO 8601 formatted date-time string.
The type of regulated county check.
The current status of the regulated county check.
pending— the check has been submitted and is awaiting results.complete— results are available.cancelled— the search was cancelled, either at your request or because it could not be completed. When a search cannot be completed, acounty_check.not_availablewebhook is delivered.
A machine-readable reason for a check's error status. Only present when the check has errored.
provider_error— the third-party data provider returned an unrecoverable error.timeout— the check did not complete within the allowed time window.cancelled— the check was cancelled, either at your request or because it could not be completed.need_more_info— additional identity information (e.g. email or SSN) is required to view results.
A reference identifier for linking related records. Limited to 64 alphanumeric characters, underscores, and hyphens.
The search criteria used for the regulated county check.
The fully-disclosed results of the regulated county check. Empty array if no records found or if the check is still pending. A record excluded by legal rules never appears here -- see excluded_records.
Records excluded by legal rules, reduced to an identifier, classification, jurisdiction, and per-charge offense classification. Present only when the account's excluded_record_disclosure setting is stripped; omitted (or empty) otherwise, and always separate from results.
An unstructured array of human-readable notes about this particular check. May contain notes about how input was parsed or other information about results. Not intended to be parsed by computer, as these notes are not guaranteed to be in any given format.
[ "used no ruleset" ]
Customer accept/decline/dispute state for a regulated check.
Present only when include[]=review is requested; omitted otherwise. Indicates whether adverse-action workflow is enabled for this product.
{ "profile_id": "2b8313e8-4efd-45a1-b578-952b8313e890" }