Skip to main content
POST
Verify user identity

Authorizations

Authorization
string
header
required

Enter your API key in the format: sk_test_xxxxx or sk_live_xxxxx

Body

application/json
workflow_key
string
default:user_verification_default
required

Workflow key to use for verification (determines required fields)

Pattern: ^[a-z0-9_]+$
Example:

"user_verification_default"

first_name
string
required

First name

Example:

"John"

last_name
string
required

Last name

Example:

"Doe"

date_of_birth
string<date>
required

Date of birth (YYYY-MM-DD)

Example:

"1990-01-15"

ssn
string
required

Social Security Number

Example:

"123-45-6789"

address_line_1
string
required

Street address line 1

Example:

"123 Main St"

city
string
required

City

Example:

"San Francisco"

region
string
required

Region (state/province/county)

Example:

"CA"

postal_code
string
required

Postal code

Example:

"94102"

reference_id
string

Your reference ID for tracking

Example:

"user_12345"

middle_name
string

Middle name or initial

Example:

"A"

email
string

Email address

Example:

"john.doe@example.com"

phone_number
string

Phone number

Example:

"+15551234567"

address_line_2
string

Street address line 2

Example:

"Apt 4B"

country
string

Country (2-letter ISO code)

Example:

"US"

metadata
object

Custom metadata.

In test mode (sk_test_ key), the reserved key _simulate drives a deterministic outcome without calling the identity provider. Value is one of:

  • Risk levels: low (default), medium, high, critical
  • Scenarios: synthetic, watchlist, dob_mismatch, no_match
  • fail → terminal status: failed

When _simulate is omitted, the reserved test SSNs still drive the outcome. Ignored in live mode.

Example:

Response

Verification completed

user_id
string<uuid>
required

ID of the user entity created or verified

Example:

"550e8400-e29b-41d4-a716-446655440000"

verification_id
string<uuid>
required

Unique verification ID

Example:

"660f9511-f30c-52e5-b827-557766551111"

status
enum<string>
required

Current status of the verification

Available options:
pending,
in_progress,
completed,
failed
Example:

"completed"

mode
enum<string>
required

Test/live partition the verification was created under. Determined by the API key used.

Available options:
test,
live
Example:

"live"

risk
object
required

Risk assessment with level and detailed reasons

match
object
required

Field-level match results (only fields included in verification request)

created_at
string<date-time>
required

ISO 8601 timestamp of when the verification was created

Example:

"2025-10-24T10:30:00Z"

reference_id
string

Your reference ID (if provided in request)

Example:

"user_12345"

synthetic
object

Synthetic identity detection results

velocity
object

Velocity checks showing frequency of identity attributes across recent requests

device
object

Device intelligence (available for session-based verifications)

watchlist
object

Watchlist screening results (sanctions, PEP, adverse media)

updated_at
string<date-time>

ISO 8601 timestamp of when the verification was last updated

Example:

"2025-10-24T10:35:00Z"