---
title: "DigiLocker aggregate (one-call convenience)"
method: POST
path: "/v1/kyc/digilocker/result/{session_id}"
tags: ["KYC"]
---

# DigiLocker aggregate (one-call convenience)

`POST /v1/kyc/digilocker/result/{session_id}`

## Request

- Base URL: `https://api.casparser.in`
- URL: `https://api.casparser.in/v1/kyc/digilocker/result/{session_id}`
- Auth: API key in header `x-api-key`

Return everything available for a DigiLocker session in a single call.
Each section is independent: if one is unavailable (e.g. the investor
didn't consent to it), it's reported under `errors` and the rest of the
response still succeeds.

- `identity` — verified identity, when requested via `documents` (free).
- `documents` — list of the investor's documents (free). Set
  `include_documents: false` to skip.
- `fetched` — for each document in `fetch_documents`, the parsed document data.

**Credits:** 0.25 per call, regardless of how many documents are
fetched or whether identity is returned.

## Path parameters

- `session_id` string, required

## Request body

- object
  - `fetch_documents` string[]: Documents to additionally fetch + parse from the locker. Default: [] (no document fetch, no fetch billing).
  - `include_documents` boolean: Include the issued-documents list.

## Response `200`

Aggregate result (sections present per availability)

- object
  - `status` string
  - `identity` DigilockerVerifiedIdentity: The investor's verified identity. Only fields the investor shared are populated. `verified` contains the authenticated document identifiers (e.g. PAN, Aadhaar number).
    - `name` string, nullable
    - `dob` string, nullable
    - `gender` string, nullable
    - `email` string, nullable
    - `mobile` string, nullable
    - `digilocker_id` string, nullable
    - `username` string, nullable: DigiLocker preferred username
    - `care_of` string, nullable
    - `address` string, nullable
    - `verified` object: Authenticated document identifiers (keys present only when verified).
      - `pan` string
      - `aadhaar` string: Usually masked
      - `driving_licence` string
  - `consent` DigilockerConsent: Consent receipt captured at session start. Carried through the flow for audit (DPDP / RBI compliance).
    - `purpose` string, nullable: The consent_purpose provided at /session.
    - `consented_at` string, date-time, nullable: ISO 8601 timestamp (UTC) when consent was captured.
  - `consented_documents` string[]: Friendly names of documents the user consented to share.
  - `documents` DigilockerDocument[]
    - `name` string: Document name
    - `type` string
    - `doctype` string: 5-character DigiLocker document type code
    - `issuer` string
    - `issuerid` string
    - `uri` string: Unique DigiLocker identifier for the document
    - `mime` string[]
    - `date` string, date, nullable: Last modified date in DigiLocker, normalized to ISO 8601.
  - `fetched` object: Parsed documents keyed by the `fetch_documents` value (pan/aadhaar/driving_licence). Value is null if the document was requested but unavailable. Each parsed object also includes a `signature` block.
    - `pan` DigilockerPan: PAN certificate data parsed from DigiLocker XML (returned as `parsed` when `parse=pan`). Any field may be null if absent in the source XML.
      - `pan` string, nullable: PAN number
      - `name` string, nullable: PAN holder name
      - `father_name` string, nullable: Father/spouse name (the `swd` field; often empty)
      - `dob` string, nullable: Date of birth (DD-MM-YYYY as returned)
      - `gender` string, nullable
      - `status` string, nullable: Certificate status (e.g. "A" = Active)
      - `verified_on` string, nullable: Timestamp DigiLocker verified the record
      - `signature` DigilockerSignature: Signature provenance for a fetched document. Reports whether a signed XML block with an X.509 certificate is present, plus the signing certificate's details. Note: this is provenance reporting, not full XML-DSIG cryptographic verification (the trust model is direct-from-source retrieval, consistent with the industry).
        - `signature_present` boolean
        - `certificate` object, nullable
          - `subject` string
          - `issuer` string
          - `valid_from` string, date-time
          - `valid_until` string, date-time
          - `serial_number` string
    - `aadhaar` DigilockerAadhaar: e-Aadhaar (Aadhaar Paperless Offline eKYC) data parsed from DigiLocker XML. Any field may be null if not present in the source XML.
      - `name` string, nullable: Full name as on Aadhaar
      - `dob` string, nullable: Date of birth (as returned by DigiLocker, typically DD-MM-YYYY)
      - `gender` string, nullable: Gender (M, F, or T)
      - `care_of` string, nullable: Care-of / guardian field
      - `address` string, nullable: Full address assembled from the Aadhaar address fields
      - `photo_base64` string, nullable: Base64-encoded photograph from the Aadhaar XML
      - `masked_aadhaar` string, nullable: Masked Aadhaar number (only last 4 digits visible)
      - `session_id` string, nullable: DigiLocker/UIDAI reference id for this eKYC document
    - `driving_licence` DigilockerDrivingLicence: Driving licence data parsed from DigiLocker XML (returned under `fetched.driving_licence`). Any field may be null if absent in the source XML.
      - `dl_number` string, nullable
      - `name` string, nullable
      - `father_name` string, nullable
      - `dob` string, nullable: Date of birth, normalized to ISO 8601.
      - `gender` string, nullable
      - `status` string, nullable
      - `issued_at` string, nullable
      - `issue_date` string, date, nullable
      - `valid_from` string, date, nullable
      - `expiry_date` string, date, nullable
      - `present_address` string, nullable
      - `permanent_address` string, nullable
      - `categories` object[]: Vehicle classes the holder is licensed for.
        - `code` string
        - `abbreviation` string
        - `description` string
        - `issue_date` string, date
      - `signature` DigilockerSignature: Signature provenance for a fetched document. Reports whether a signed XML block with an X.509 certificate is present, plus the signing certificate's details. Note: this is provenance reporting, not full XML-DSIG cryptographic verification (the trust model is direct-from-source retrieval, consistent with the industry).
        - `signature_present` boolean
        - `certificate` object, nullable
          - `subject` string
          - `issuer` string
          - `valid_from` string, date-time
          - `valid_until` string, date-time
          - `serial_number` string
  - `errors` object: Per-section error codes (omitted when there are none).

## Other responses

- `401`: Unauthorized. This can happen if the `x-api-key` header is missing.

## Changes

- **2026-09-13** `cf1b57c0f2f7`: 1 warning
  - the optional response header `X-Request-ID` removed for the status `401`
- **2026-08-30** `a38ebe1b68cb`: 1 info
  - the endpoint scheme security `AccessTokenAuth` was removed from the API
- **2026-07-12** `c74b9ecd5b53`: 1 info
  - endpoint added

[Operation history](https://skmtc.dev/casparser/apis/cas-parser-track-portfolios-from-cdsl-nsdl-cams-kfintech-2/changes/v1/kyc/digilocker/result/:session_id/post.md)

---

[API](https://skmtc.dev/casparser/apis/cas-parser-track-portfolios-from-cdsl-nsdl-cams-kfintech-2.md) - [All operations](https://skmtc.dev/casparser/apis/cas-parser-track-portfolios-from-cdsl-nsdl-cams-kfintech-2/llms.txt) - [OpenAPI document](https://skmtc.dev/casparser/apis/cas-parser-track-portfolios-from-cdsl-nsdl-cams-kfintech-2/revisions/9d8f1445bad3?raw)
