Choose the document workflow before you choose an API. DigiLocker serves personal document workflows. EntityLocker serves organisational documents. API Setu helps organisations discover, publish, and request access to APIs. API Setu overview DigiLocker partner resource centre EntityLocker resources

The same company can play different roles across its products. A university can issue awards. Its admissions team can also verify awards from other institutions.

Start with the record and the actor

You need to	Start with	Actor and decision
Receive an issued personal document	DigiLocker requester route	The person grants access for the proposed use
Publish records your institution issues	DigiLocker issuer route	The institution controls the source record
Work with company records	EntityLocker	An authorised representative acts for the entity
Find an API or request a subscription	API Setu	Your organisation applies for the relevant publisher's access
Verify a candidate's academic award	National Academic Depository	An approved verifier follows the candidate consent process

Meri Pehchaan appears in the DigiLocker requester specification. Use the applicable authorization contract to separate the identity response from the grant to retrieve documents. Requester v2.4 specification

Walk through a company onboarding example

A marketplace wants to onboard a company and its delivery staff. The company supplies business records. A manager accepts responsibilities for the company. An individual driver supplies licence evidence.

Those are three decisions. The company evidence identifies the business. The application checks whether the manager may act for it. The licence evidence relates to the individual driver and the proposed assignment.

Create separate records for each decision. A verified organisation record cannot establish the driver's licence status. A driver check also leaves the manager's authority unresolved.

Choose an implementation path

Name the record and its authoritative source.
Decide whether your organisation issues or requests the record.
Identify who can share it for this purpose.
Find the applicable provider documentation.
Confirm your organisation's access route.
Define the application decision that follows retrieval.

If the task is signing a new agreement, evaluate a signing service. If the task is assessing financial onboarding, ask the responsible entity which evidence route it accepts. DigiLocker and eSign workflow comparison.

Keep names clear in your plan

API Setu is the government platform. The commercial Setu service has its own API documentation and terms. Identify the actual service and contracting entity when you compare integration options. Commercial Setu documentation.

For technical implementation, choose the contract before building the consent redirect. For organisation access, prepare the use case and supporting information first. API Setu application worksheet.

Continue with your current task

If you are working on	Read next
A requester integration	DigiLocker requester guide
An existing DigiLocker client	Version 2.4 migration guide
A company's document inventory	EntityLocker for recognised startups
University award publication	University certificate issuance
Academic record checks	NAD candidate consent workflow
Evidence for an onboarding decision	Driving licence result guide

Map your workflow with NamoID

NamoID engineers can help map sign-in, document access, and the application decision in a single workflow diagram. Share the actors, record types, and stack in Slack. Message the NamoID team in Slack