KYC
DigiLocker Initiate
Start a DigiLocker-based Aadhaar verification - returns the authorization link and an access_request_id for the customer to complete OAuth.
POST
DigiLocker initiate
Starts a DigiLocker-based Aadhaar verification. Returns the DigiLocker authorization link and an
access_request_id. Redirect the customer to the link to complete OAuth on the DigiLocker portal, then finalize with DigiLocker Verify.
Authenticate with your parent main account’s
X-Auth-ID and X-Auth-Token — the same credentials used everywhere else in the API.Initiate
Call this endpoint with your
redirect_url (and optional oauth_state). Capture access_request_id and send the customer to the returned auth_url.Customer completes OAuth
The customer authorizes on the DigiLocker portal and is returned to your
redirect_url.Verify
Call DigiLocker Verify with the
access_request_id.Request body
| Field | Type | Required | Description |
|---|---|---|---|
redirect_url | string (URI) | Yes | Where DigiLocker returns the customer after OAuth. |
oauth_state | string | No | Opaque value echoed back on the redirect — use it for CSRF protection by comparing it to a value you stored before redirecting. |
Response example
200 OK
Store the
access_request_id against the customer’s session before redirecting. The OAuth round-trip happens in the customer’s browser; you finalize server-side in the next step using this id.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
DigiLocker authorization link