Create a verification session and mint its end-user session token
POST/v1/verifications
Server-side call with a dv_sk_* key. Returns the verification and a dv_tok_* bound to it; ship the token to the end user's app and have it call the document and liveness endpoints as usual. Results made with that token are recorded as this verification's steps.
Request
Responses
- 201
- 400
- 401
- 403
- 429
Default Response
Default Response
Default Response
Default Response
Default Response
SDK usage
// not exposed in the v2 SDK yet; call POST /v1/verifications from your server, then hand `session.token` to the app.
// not exposed in the v2 SDK yet; the app uses the `session.token` your server received from POST /v1/verifications for every step.
Example
curl -X POST https://api.drukverify.com/v1/verifications \
-H "Authorization: Bearer dv_sk_test_..." \
-H "Content-Type: application/json" \
-d '{"customer_ref":"user_42","policy":{"liveness_mode":"challenge"}}'