Pull Document Support in Digilocker SDK

[tushar5526]

Description

Pull document support for digilocker SDK. Digilocker supports pulling in documents from issuers and storing them in Digilocker through APIs. This issue focuses on giving a POC on how we can have to pull document functionality integrated with the current SDK design and then its implementation.

Goals

• Propose updates in the current design of SDK to support pull documents API
• Implementation of the discussed design

Expected Outcome

• Users can pull documents from issuers via API calls.

Acceptance Criteria

• User specifies which document to pull and makes a function call.
• Pull parameters are returned back from SDK to the user
• The user then specifies the values for pull parameters and makes another call
• The user gets a proper response if a pull document request fails or succeeds

Implementation Details

• Pulling a document requires a few basic things - doctype, orgid, pull parameters, digilocker acess token
• doctype can be specified by the user - Digilocker also provides a list of doctypes - Getting a list of files using Digilocker APIs also returns back associated doctypes.
• orgid can be fetched from LIst of Issuers API from digilocker APIs
• pull parameters are also fetched from Digilocker APIs and specify the parameters (applicationID, certificate Number etc) required to pull documents.

Mockups / Wireframes

NA

---

Project

Digilocker-SDK

Organization Name:

Samagra

Domain

Social Welfare

Tech Skills Needed:

TS, JS

Mentor(s)

@tushar5526 @ChakshuGautam @Shruti3004

Complexity

Medium

Category

PoC

Sub Category

API, Backend