Account lookup
Optionally check a mobile number or Aadhaar number to choose a sign-in or sign-up path.
Guide an investor through DigiLocker authorization and retrieve available identity, issued documents, and parsed Aadhaar, PAN, or driving-licence data.
Each API operation has one job, so your product controls the user experience and the processing boundary.
Optionally check a mobile number or Aadhaar number to choose a sign-in or sign-up path.
Capture explicit consent and purpose, then receive the authorization URL and session ID.
Redirect the investor to DigiLocker and back to your callback with state and session context.
Fetch identity, available issued documents, parsed data, and section-level errors in one aggregate call.
Identity, issued-document inventory, and parsed-document sections are independent. An unavailable section is reported under errors without failing every other result.
POST /v1/kyc/digilocker/session
{
"consent": true,
"consent_purpose": "KYC for account opening",
"redirect_url": "https://yourapp.com/callback"
}The session requires explicit consent, a clear purpose, and your redirect URL. The authorization happens on DigiLocker, not inside a simulated identity screen.
DigiLocker retrieves consented identity and documents. PAN KYC Status checks registry state across the KRAs.
Explore KYC StatusThe aggregate result can parse available PAN, Aadhaar, and driving-licence documents, alongside verified identity and the issued-document list.
Yes. Starting a session requires explicit consent and a consent purpose, and the investor authorizes access on DigiLocker.
No. It is an optional pre-consent check that can help your product choose between DigiLocker sign-in and sign-up.
No. Identity, issued documents, and parsed-document sections are independent; unavailable sections are returned under errors.
Map authorization, callback state, document handling, and retention before production.