DigiLocker API Integration
Pull government-issued documents — driving licence, RC, marksheets — directly from issuers with citizen consent.
What DigiLocker API integration does
DigiLocker changes the economics of document collection. Instead of asking a customer to photograph a document, uploading it, running OCR over it and having a human confirm it is genuine, you request the document from the authority that issued it, with the citizen's consent, and receive it already verified.
That removes two steps and one entire risk category. The upload step — the most common abandonment point in Indian digital onboarding — disappears. The verification queue disappears with it, because a document fetched from its issuer does not need to be checked for authenticity. And forged-document fraud becomes structurally impossible for the document types you fetch this way, rather than something you are trying to detect after the fact.
Issued documents available through DigiLocker commonly include driving licences, vehicle registration certificates, PAN cards, academic marksheets, insurance policies and various certificates, subject to the issuing authority publishing them.
What teams build with it
Upload-free onboarding
Request exactly the documents you need with consent and receive them issuer-verified, removing both the upload and the manual verification step.
Licence and RC verification
Pull driving licences and registration certificates directly for driver and vehicle onboarding.
Academic credential checks
Fetch marksheets and certificates for admissions or employment screening.
Claims and policy documentation
Retrieve supporting documents for insurance claims without a document-chase cycle.
Endpoints included
GET/digilocker/v1/issued-documentsReturns the list of documents issued to the authenticated DigiLocker account.
Try it in the sandbox
https://sandbox.aeologic.io/digilocker/v1/issued-documents{
"access_token": "dl_at_••••••3f9a"
}What you need before we start
- The document types your flow requires, and confirmation the issuers publish them
- A consent screen that names the documents being requested
- A fallback path for customers who decline or hold no DigiLocker account
How we deliver it
- Document-type scoping against issuer availability
- Consent flow design and review
- Sandbox integration with synthetic issued documents
- Production rollout with graceful fallback to manual upload
Related Documents & Signing integrations
Industries using DigiLocker
Solution bundles that use it
DigiLocker API integration — FAQs
Which documents can we pull?
Any issued document type the citizen holds from a participating issuer, and only with their explicit consent for that request. Availability depends on the issuing authority having published the type to DigiLocker.
Are fetched documents pre-verified?
Yes — they come from the issuer rather than from the customer, which is precisely why they do not need separate authenticity checking.
What if the customer declines consent?
The request returns a declined status and no data is transmitted. Your flow should fall back to manual upload, and our connector surfaces the decline explicitly rather than as a generic failure.
Is DigiLocker free to integrate?
It is a public-access rail with no scheme licensing cost; you are paying for the integration, consent handling and reliability.
Ship DigiLocker in days
Tell us your stack and we'll wire up DigiLocker API integration for your team.
Talk to Aeologic