---
title: "Get DigiLocker user details"
method: POST
path: "/verify/digilocker/user_details"
tags: ["DigiLocker"]
---

# Get DigiLocker user details

`POST /verify/digilocker/user_details`

Fetches user details from DigiLocker using a reference_key. Requires X-API-KEY and X-Client-ID headers.

## Request body

- DigilockerUserDetailsRequest
  - `reference_key` string, required — Reference key obtained from /digilocker/get_reference.

## Response `200`

DigiLocker user details

- DigilockerUserDetailsResponse
  - `status` string, required — Overall API response status
  - `user` DigilockerUserDetailsUser, required
    - `digilockerid` string, uuid, required — DigiLocker user identifier
    - `name` string, required — User's full name
    - `dob` string — Date of birth. Provider may return YYYY-MM-DD or DDMMYYYY.
    - `gender` string — Gender code (e.g., 'M','F','O')
    - `eaadhaar` string — Flag indicating eAadhaar presence ('Y'|'N')
    - `reference_key` string — Reference key associated with the user record
    - `mobile` string — Mobile number in 10-digit format (sanitized in examples)
    - `picture` string — Base64-encoded profile picture (data URI or raw base64).
    - `email` string, email — User email address (when available)
  - `chargeble` string — Indicates if the operation is chargeable ('true'|'false')
  - `user_consent` string — Indicates whether user consent was recorded ('true'|'false')

## Other responses

- `400` — Invalid input or missing reference_key
- `401` — Unauthorized - missing/invalid API key or client id
- `404` — Reference key not found or expired
- `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)