DigiLocker Issuer APIs
This document provides detailed specification of the Digital Locker Pull APIs. The Pull model of integration with Digital Locker enables a Digital Locker user…
Government & public#openapi#open-data
Fork copies the collection into your workspace, without the publisher's secrets, so you can add your own key and send requests. Star saves it to your starred APIs (Account › Marketplace) and helps others find it.
Overview
This document provides detailed specification of the Digital Locker Pull APIs. The Pull model of integration with Digital Locker enables a Digital Locker user to search a document/certificate from issuer repository and fetch (pull) it into Digital Locker. The issuer departments can use these APIs for the documents that are not Aadhaar seeded. The issuer organization integrating with Digital Locker maintains the documents/certificates in its own repository (database or file system). The issuer application provides APIs to Digital Locker to access the documents in this repository. Each issuer organization will have to implement 2 APIs to integrate with the Digital Locker system.
Endpoints 2
APIs
- POSTPull Doc Request API.
/Your Pull DOC Request API PathThe Pull Doc Request API has to be implemented by the issuers and will be consumed by Digital Locker system. This API will be invoked when the resident clicks… - POSTPull URI Request API .
/Your Pull URI Request API PathThe Pull URI Request API has to be implemented by the issuers and will be consumed by Digital Locker application. This API will be invoked when a citizen…
API details
- Authentication
- None declared in the description
- Operations
- 2 operations on 2 pathsPOST 2
- Main resources
- APIs 2
- Response formats
application/xml- Description format
- OpenAPI 3.0.2, API version
3.0.0 - Links
- OpenAPI document · Terms of service
- Listed from
- APIs.guru OpenAPI Directory (CC0-1.0)
Source updated
How to test the DigiLocker Issuer APIs in Swastik Codes
- Open the APISelect “Fork & run in Swastik Codes” on this page. Sign in or create a free account if asked.
- Fork it into your workspaceChoose a workspace. You get your own copy of the DigiLocker Issuer APIs collection, without the publisher's secrets.
- Add your credentialsOpen the collection's variables or an environment and enter your API key or token, if the API needs one.
- Send a requestPick an endpoint, for example “Pull Doc Request API.” (POST /Your Pull DOC Request API Path), and press Send. Check the response, add tests and run the whole collection with the runner.
Frequently asked questions
What is the DigiLocker Issuer APIs?
This document provides detailed specification of the Digital Locker Pull APIs. The Pull model of integration with Digital Locker enables a Digital Locker user… It is listed under Government & public and has 2 endpoints.
Who publishes the DigiLocker Issuer APIs?
It is listed from API Setu's public API description (an OpenAPI document), not published by API Setu on Swastik Codes. Anyone who controls apisetu.gov.in can claim the profile by adding a DNS TXT record.
How do I authenticate with the DigiLocker Issuer APIs?
Its OpenAPI description does not declare an authentication scheme. Some endpoints may be open; check the provider's documentation before relying on that.
How many endpoints does the DigiLocker Issuer APIs have?
2 operations on 2 paths (2 POST). The largest groups are APIs.
Is forking the DigiLocker Issuer APIs free?
Yes. Forking copies the collection into your workspace for free. It has been starred 0 times and forked 0 times.