---
title: "Verify DigiLocker account"
method: POST
path: "/verify/digilocker/verify_account"
tags: ["DigiLocker"]
---

# Verify DigiLocker account

`POST /verify/digilocker/verify_account`

Verifies a DigiLocker account using mobile number.

| HTTP Status | Code  | Reason            | Message                        | Merchant Action                        |
|-------------|-------|-------------------|---------------------------------|----------------------------------------|
| 200         | 2002  | ACCOUNT_NOT_FOUND | No DigiLocker account linked.   | Skip DigiLocker or redirect to sign-up.|
| 200         | 1004  | ACCOUNT_FOUND     | DigiLocker account exists.      | Proceed with initiate session.         |
| 400         | 3000  | INVALID_INPUT     | Mobile number invalid/missing.  | Validate input and retry.              |

## Request body

- DigilockerVerifyAccountRequest
  - `mobile_number` string, required — Mobile number in 10-digit format.

## Response `200`

Lookup result

- DigilockerVerifyAccountResponse
  - `status` string, required — Overall API response status
  - `code` integer, required — Provider-specific response code
  - `result` DigilockerVerifyAccountResult
    - `registered` boolean, required — Whether the mobile number is registered with DigiLocker
    - `digilockerid` string, uuid — DigiLocker user identifier (UUID)
    - `source` string — Source/provider of the record
  - `chargeble` string — Indicates if the operation is chargeable ('true'|'false')
  - `user_consent` string — Indicates if user consent was obtained ('true'|'false')

## Other responses

- `400` — Invalid input
- `401` — Unauthorized - missing/invalid API key or client id
- `500` — Internal server error

---

[API](https://skmtc.dev/idto/apis/verification-api.md) · [All operations](https://skmtc.dev/idto/apis/verification-api/llms.txt) · [OpenAPI document](https://skmtc-service-production.skmtc.workers.dev/v1/apis/idto/verification-api/revisions/e3d57dab8db4/schema)