canonical: https://jentic.com/apis/apisetu.gov.in

# API Setu APIs

API Setu is the Government of India's API gateway for citizen-facing document services, connected to the DigiLocker platform. Its endpoints let integrators fetch government-issued qualification and eligibility documents as digitally signed, verifiable records instead of collecting scanned uploads. This vendor groups two API Setu issuers: the Agricultural Scientists Recruitment Board (ASRB), which issues NET merit certificates, and the Kerala Public Service Commission (KPSC), which issues One Time Verification certificates. Both return DigiLocker-compatible payloads signed at the issuing authority, so downstream systems can trust the credential without a separate check.

## For AI agents

An agent can fetch government-issued verification documents from API Setu, retrieving ASRB NET merit certificates and Kerala PSC One Time Verification certificates as DigiLocker-compatible signed records for a given candidate. Each API returns a tamper-evident payload the agent can attach to a recruitment, appointment, or background-check workflow.

## Scope

Use for: Fetching DigiLocker-compatible ASRB NET merit certificates and Kerala PSC One Time Verification certificates as signed government documents

Not supported:
- exam registration
- application submission
- rank-list publication
- admission tickets
- real-time streaming

## APIs

| API | Category | Endpoints | Description |
| --- | --- | --- | --- |
| Agricultural Scientists Recruitment Board | education | 1 | Fetch ASRB NET merit certificates for a candidate as a verified digital document via API Setu and DigiLocker. |
| KERALA PUBLIC SERVICE COMMISSION, Kerala | identity-auth | 1 | Issue Kerala PSC One Time Verification certificates to candidates as DigiLocker-compatible verified documents. |

## Which API to use

| Need | API | Why |
| --- | --- | --- |
| Fetch an ASRB NET merit certificate for an agricultural scientist recruitment candidate | asrb | The ASRB endpoint issues central-government NET-I and NET-II 2019 merit certificates via POST /mrcer/certificate. |
| Fetch a Kerala PSC eligibility certificate for a state government appointment | main | The Kerala PSC endpoint issues One Time Verification certificates via POST /otcer/certificate for state public-service candidates. |

## Cross-API use cases

### Unified candidate credential verification

A recruitment or verification platform operating across Indian government hiring can pull both a candidate's ASRB NET merit certificate and their Kerala PSC One Time Verification certificate through one integration. Because both come back as DigiLocker-compatible signed documents, the platform can compile a verified qualification bundle without collecting scanned uploads.

Example prompt: For a candidate, fetch the ASRB NET merit certificate and the Kerala PSC OTV certificate, then return both signed records as a combined credential bundle.

### DigiLocker document aggregation

A DigiLocker partner application that surfaces a citizen's verified government records can list both agricultural recruitment and Kerala public-service certificates from the same API Setu integration. Each certificate is issued once and reused across the citizen's future job and departmental submissions.

Example prompt: Retrieve the ASRB merit certificate and the Kerala PSC OTV certificate for a citizen and store both issued document references in their DigiLocker wallet.

## Why Jentic

- **Setup:** Wiring API Setu by hand means provisioning each issuer's key pair, packaging each certificate request, and parsing each signed response yourself. Through Jentic you install once, add the ASRB and Kerala PSC APIs from the Jentic directory, store the credentials once, and your agent calls either issuer.
- **Permission scoping:** Each API exposes a single certificate-retrieval operation, and because you run Jentic One yourself your own rules decide which operations the agent may use. You can allowlist just the ASRB fetch, just the Kerala PSC fetch, or both, so the agent can only call the issuers you have added.
- **Credential handling:** Your API Setu key and client id for each issuer are stored once, encrypted, by your own Jentic One instance and injected at execution time. They never enter the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'fetch a candidate's government verification certificate', and Jentic returns the matching ASRB or Kerala PSC operation with its input schema so the agent calls the right issuer without browsing the API Setu documentation.

## Related vendors

- **Factorial HR** — Attaches verified government certificates to an employee record once recruitment or appointment completes.
- **Clio** — Files verified government certificates against a matter when a legal workflow needs documentary proof.

## FAQ

### What is API Setu and how does it relate to DigiLocker?

API Setu is the Government of India's gateway for citizen-facing document services. Its issuer endpoints return records that are compatible with DigiLocker, India's national platform for storing verified government documents. When you fetch a certificate through an API Setu endpoint, you receive a signed payload that can be stored in or presented from a DigiLocker wallet.

### Which document types can I retrieve across these APIs?

Two document types are exposed here. The ASRB endpoint issues NET-I and NET-II 2019 merit certificates for agricultural scientist recruitment, and the Kerala PSC endpoint issues One Time Verification certificates for state public-service candidates. Each API exposes a single certificate-issuing operation.

### Do the ASRB and Kerala PSC APIs share credentials?

They share the same credential model, the X-APISETU-APIKEY and X-APISETU-CLIENTID header pair issued by API Setu at onboarding. The keys themselves are scoped per issuer, so you provision ASRB and Kerala PSC credentials separately rather than reusing one set across both.

### Are the returned certificates actually verifiable, or just raw data?

They are verifiable. Both endpoints return a certificate payload digitally signed at the issuing authority, so downstream systems can present it as a trusted government document rather than as unverified JSON. This removes the need to independently re-check the qualification claim.

### What are these APIs not suitable for?

They do not handle exam registration, application submission, rank-list publication, or admission tickets. Each covers only the retrieval of an already-issued certificate for a qualified candidate, and each is limited to the specific document type its issuer exposes.

### How does an agent choose between the ASRB and Kerala PSC endpoints?

Use the ASRB endpoint when the workflow needs central-government agricultural recruitment proof, and use the Kerala PSC endpoint when it needs Kerala state public-service eligibility proof. An agent can search by intent and Jentic returns the matching operation with its input schema, so it calls the right issuer for the candidate at hand.