Required details to create a verification session
IdRamp Identity Verification API - Overview (1.0)
The IdRamp Identity Verification API enables applications to initiate, monitor, and retrieve identity verification sessions using trusted verification providers integrated with IdRamp. It also includes a flexible rules-based matching utility for comparing and validating identity data.
Start Verification (
POST /api/v1/verification): Create a new verification session for a user, specifying the IdRamp Identity Verifier configuration to use. Returns a session identifier and a provider URL where the verification flow begins.Get Verification Status (
GET /api/v1/verification/{identityVerifierId}/status/{verificationId}): Retrieve the current state of a verification session (started,completed). Useful for polling the session progress without fetching detailed results.Get Verification Result (
GET /api/v1/verification/{identityVerifierId}/{verificationId}): Fetch the full verification outcome once a session completes, including status (success,fail,canceled), provider user ID, and verified user traits such as name, email, phone, and document information.Match Utility (
POST /api/v1/verification/match): Evaluate custom rules to compare and match data across two records (e.g., source vs. target). Supports logical and fuzzy matching (e.g., equality, Levenshtein ratio) with detailed per-rule results.
- Client calls Start Verification to create a session and obtain the provider launch URL.
- End-user completes verification via the provider interface.
- Client waits for user to be redirected back to
returnUrlspecified at Start signalling completion. Alternatively, the Client polls Get Status until completion. - Once completed, client calls Get Result to retrieve verified attributes.
- Optionally, client uses Match Utility to compare verified data with existing records.
https://idvtest.idramp.com/
Request
Starts a new identity verification session using the specified IdRamp Identity Verifier instance.
How it works
- Provide the
identityVerifierIdfor the IdV configuration you want to use. - Provide a
returnUrl. If verification succeeds, the user is redirected to this URL. customFieldscan carry additional key–value metadata required by your client workflow.
Successful response (200)
- Returns
StartVerificationResponseDtowith:id: the server-generated verification session identifier.status: the current session status.startUrl: a URL your client/app can open to begin the provider’s verification flow.
Errors
- 401/403: missing or invalid API key, or insufficient policy.
- 422: request body failed validation (see
ErrorResponse).
Auth
- Requires
x-api-keywith theApiKeyPolicy.
The IdRamp IdentityVerifier instance id to use for this session.
If present, users will be redirected to this url upon successful verification.
- Test server
https://idvtest.idramp.com/api/v1/verification
- curl
- JavaScript
- Node.js
- Python
- Java
- C#
- PHP
- Go
- Ruby
- R
- Payload
curl -i -X POST \
https://idvtest.idramp.com/api/v1/verification \
-H 'Content-Type: application/json' \
-H 'x-api-key: YOUR_API_KEY_HERE' \
-d '{
"identityVerifierId": "b655c3c4-cff2-4521-8835-54c696aaa24d",
"returnUrl": "https://idramp.com",
"customFields": {}
}'{ "id": "string", "status": "string", "startUrl": "string" }
Request
Returns the lightweight status of a verification session, suitable for polling.
Path parameters
identityVerifierId(UUID): IdRamp Identity Verifier instance ID used to start the session.verificationId(string): The session ID returned by the start call.
Successful response (200)
- Plain string status:
startedorcompleted.
When to use
- Use this endpoint to check whether the session has finished without fetching the full result payload.
Errors
- 400/422: invalid parameter format (see
ProblemDetails). - 401/403: authentication/authorization failure.
- 404: session not found for the given IDs.
Auth
- Requires
x-api-keywith theApiKeyPolicy.
- Test server
https://idvtest.idramp.com/api/v1/verification/{identityVerifierId}/status/{verificationId}
- curl
- JavaScript
- Node.js
- Python
- Java
- C#
- PHP
- Go
- Ruby
- R
- Payload
curl -i -X GET \
'https://idvtest.idramp.com/api/v1/verification/{identityVerifierId}/status/{verificationId}' \
-H 'x-api-key: YOUR_API_KEY_HERE'"string"
Request
Retrieves the verification outcome and captured traits for a completed session.
Path parameters
identityVerifierId(UUID): IdRamp Identity Verifier instance ID used to start the session.verificationId(string): The session ID returned by the start call.
Successful response (200)
- Returns
VerificationResultDto, including:status: one ofsuccess,fail, orcanceled.user_id: the provider’s unique user identifier (if available).email,phone: top-level contact values, when present.traits: structured attributes (e.g.,first_name,last_name, nesteddocument).
Notes
- Call after status indicates completion to obtain final details.
- Field presence varies by provider and configuration.
Errors
- 401/403: authentication/authorization failure.
- 422: parameter formatting or validation error (see
ErrorResponse).
Auth
- Requires
x-api-keywith theApiKeyPolicy.
- Test server
https://idvtest.idramp.com/api/v1/verification/{identityVerifierId}/{verificationId}
- curl
- JavaScript
- Node.js
- Python
- Java
- C#
- PHP
- Go
- Ruby
- R
- Payload
curl -i -X GET \
'https://idvtest.idramp.com/api/v1/verification/{identityVerifierId}/{verificationId}' \
-H 'x-api-key: YOUR_API_KEY_HERE'{ "email": "string", "phone": "string", "user_id": "string", "status": "string", "traits": { "first_name": "string", "last_name": "string", "email": "string", "phone": "string", "document": { … } } }