KYC
DigiLocker Verify
Finalize Aadhaar verification via DigiLocker after the customer completes the OAuth flow.
POST
DigiLocker verify
Finalizes the Aadhaar verification via DigiLocker after the customer completes OAuth. Pass the
Call this only after the customer has completed the DigiLocker OAuth flow. Calling it before the customer authorizes will not return
access_request_id from DigiLocker Initiate. linked_number is optional (92-series per-number binding).
Authenticate with your parent main account’s
X-Auth-ID and X-Auth-Token — the same credentials used everywhere else in the API.Request body
| Field | Type | Required | Description |
|---|---|---|---|
access_request_id | string | Yes | The id returned by DigiLocker Initiate. |
linked_number | string | No | Optional. Binds the Aadhaar to a specific 92-series number (e.g. +91XXXXXXXXXX). |
Response example
200 OK
verified.Authorizations
Your Vobiz account Auth ID
Your Vobiz account Auth Token
Path Parameters
The sub-account's Auth ID.
Example:
"SA_XXXXXX"
Body
application/json
Response
200 - application/json
Verification result
Outcome of a single KYC verification step.
Available options:
pan, gst, cin, aadhaar Available options:
verified, failed, pending Recomputed sub-account call-blocking state after this verification.
Present and true on responses from the test-mode endpoints.