Request data model
View field support, webhooks, and list parameters for each integration on the Supported Integrations page.
| Field | Type | Required | Description |
|---|---|---|---|
id | string | No | (read-only) |
created_at | string (date-time) | No | (ISO-8601 / YYYY-MM-DDTHH:MM:SSZ format) (read-only) |
updated_at | string (date-time) | No | (ISO-8601 / YYYY-MM-DDTHH:MM:SSZ format) (read-only) |
package_id | string | No | |
parameters | VerificationParameterInput[] | No | |
parameters[].id | string | No | |
parameters[].name | string | No | name of parameter |
parameters[].inputs | string[] | No | |
target_url | string | No | |
candidate_id | string | No | points to ATS Candidate |
profile_ip_address | string | No | XXX.XXX.XXX.XXX |
profile_name | string | No | |
profile_date_of_birth | string | No | YYYY-MM-DD |
profile_addresses | VerificationAddress[] | No | |
profile_addresses[].address1 | string | No | |
profile_addresses[].address2 | string | No | |
profile_addresses[].city | string | No | |
profile_addresses[].region | string | No | Regional area of the employee's address. For example, in the U.S., the region is the employee's state; in Canada, the region is the employee’s province. |
profile_addresses[].region_code | string | No | Short form for the regional area of the employee's address. For example, in the U.S., the region code is the two-letter abbreviation for the employee’s state; in Canada, the region is the two-letter abbreviation for the employee's province. |
profile_addresses[].postal_code | string | No | |
profile_addresses[].country | string | No | |
profile_addresses[].country_code | string | No | Country code for the country, in ISO 3166 A-2 format |
profile_gender | enum | No | Values: MALE, FEMALE, INTERSEX, TRANS, NON_BINARY |
profile_emails | string[] | No | |
profile_telephones | string[] | No | |
profile_national_identifier | string | No | |
response_completed_at | string (date-time) | No | (ISO-8601 / YYYY-MM-DDTHH:MM:SSZ format) |
response_expires_at | string (date-time) | No | (ISO-8601 / YYYY-MM-DDTHH:MM:SSZ format) |
response_issued_at | string (date-time) | No | datetime that identify was issued (ISO-8601 / YYYY-MM-DDTHH:MM:SSZ format) |
response_status | enum | No | Background checks and compliance checks return CLEARFLAGGED or PASS/FAIL or YES/NO Values: COMPLETED, FAILED, PASSED, PENDING |
response_score | number | No | Identity verification services provide confidence scores (e.g., 0-100), Credit checks return specific numeric scores (e.g., FICO score 300-850), Fraud prevention tools use risk scores (e.g., 1-999) |
response_redirect_url | string | No | Most modern IDV providers (like Onfido, Veriff, Jumio, ID.me). Background Check Providers, such as Checkr, GoodHire, Sterling, and HireRight. Credit bureaus and services often require direct user consent and information. This allows them to properly handle disclosures required by regulations like FCRA. Employment and Education Verification need users to confirm previous employers and schools. |
response_download_urls | string[] | No | report download |
response_details | VerificationResponseDetail[] | No | |
response_details[].title | string | No | |
response_details[].text | string | No | |
response_details[].is_private | boolean | No | |
response_details[].is_failed_reason | boolean | No | |
response_details[].parameter_id | string | No | in reference to the parameter input |
response_details[].download_url | string | No | |
response_source | string | No |
Are we missing anything? Let us know