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

# Apisetu KERALA PUBLIC SERVICE COMMISSION, Kerala

The Kerala Public Service Commission (KPSC) API on API Setu issues verifiable digital documents to government job candidates and serving employees. Through DigiLocker integration it currently exposes the One Time Verification (OTV) certificate, with admission tickets and departmental test certificates also covered by the broader programme. Integrators can fetch the OTV certificate as a signed document payload rather than asking applicants to upload scans.

## For AI agents

Issue Kerala PSC One Time Verification certificates to candidates as DigiLocker-compatible verified documents.

## Scope

Does not handle exam registration, rank-list publication, or admission tickets - use for retrieving Kerala PSC One Time Verification certificates only.

## Capabilities

- Issue a Kerala PSC One Time Verification (OTV) certificate as a digitally signed document
- Authenticate calls with the X-APISETU-APIKEY and X-APISETU-CLIENTID header pair
- Replace manual document scanning with a tamper-evident government record
- Surface KPSC qualification proofs inside DigiLocker partner applications
- Embed verified appointment-eligibility documents into recruitment workflows

## Use cases

### Government Appointment Verification

Kerala state government departments appointing candidates from PSC rank lists can pull the OTV certificate directly from API Setu instead of waiting for paper documents. The single operation returns a signed DigiLocker payload that proves the candidate has cleared the PSC-side scrutiny on qualifications, age, and eligibility.

Example prompt: Call POST /otcer/certificate with the candidate's PSC identifiers, retrieve the OTV certificate, and attach it to the appointing department's onboarding record.

### DigiLocker Citizen Wallet Issuance

DigiLocker partner apps that aggregate citizens' verified government documents can list KPSC OTV certificates alongside academic and identity records. Once issued, the certificate stays available in the citizen's DigiLocker wallet for future job applications and departmental submissions.

Example prompt: Authenticate with X-APISETU-APIKEY and X-APISETU-CLIENTID, request the OTV certificate for a candidate, and store the issued document in the user's DigiLocker wallet.

### Recruitment Background Check

Background-check vendors and HR-tech platforms operating in Kerala can replace manual KPSC certificate uploads with a programmatic fetch. Because the source is the issuing authority, the result is treated as authoritative and reduces back-and-forth with the candidate.

Example prompt: Retrieve a candidate's OTV certificate as part of a background-check workflow and surface the result alongside other verified credentials.

### AI Agent Document Retrieval

An AI agent helping a citizen complete a Kerala government appointment can call the KPSC API through Jentic without exposing API Setu credentials in its context. Jentic returns the single operation by intent search and handles header injection, so the agent only needs to pass through the candidate's PSC reference.

Example prompt: Search Jentic for 'fetch Kerala PSC OTV certificate', load the schema, and execute it with the candidate's PSC identifiers.

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | /otcer/certificate | Issue a Kerala PSC One Time Verification (OTV) certificate. |

## Key resources

- **OTV Certificate** — Issue a digitally signed Kerala PSC One Time Verification certificate via the single POST /otcer/certificate operation.

## Why Jentic

- **Setup:** Wiring the Kerala PSC verification API by hand means managing two API Setu headers (X-APISETU-APIKEY and X-APISETU-CLIENTID) and handling the single certificate POST correctly. Through Jentic you install once, import the Kerala PSC API from the API Directory, store both API Setu credentials once, and your agent calls it.
- **Permission scoping:** This API exposes a single operation, POST /otcer/certificate, so you limit the agent to just that one certificate-retrieval call and nothing else in the API Setu surface. You choose the operations it may call, so the agent can only fetch One Time Verification certificates, not anything you have not added.
- **Credential handling:** Your API Setu API key and client id 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 'get a Kerala PSC OTV certificate', and Jentic returns the POST /otcer/certificate operation with its input schema so the agent calls the right endpoint without browsing the API Setu documentation.

## Related APIs

- **Agricultural Scientists Recruitment Board** — Sister API Setu endpoint that issues ASRB NET merit certificates via DigiLocker.
- **Factorial HR API** — Attach verified KPSC OTV certificates to an employee record after appointment.
- **Clio API** — File verified government certificates against a matter when legal workflows require documentary proof.

## FAQ

### What authentication does the Kerala PSC API use?

The KPSC endpoint requires the X-APISETU-APIKEY and X-APISETU-CLIENTID headers issued by API Setu during integrator onboarding. Through Jentic, both values are stored encrypted in the vault and injected at call time, so they never appear in the agent's prompt or logs.

### Can I fetch admission tickets or departmental test certificates with this API?

Not from this spec. The OpenAPI surface here exposes only POST /otcer/certificate (the One Time Verification certificate). Admission tickets and departmental test certificates are documented as part of the wider KPSC DigiLocker programme but are not endpoints in this version of the API.

### What are the rate limits for the Kerala PSC API?

Rate limits are not declared in the spec; API Setu negotiates throughput per integrator during onboarding. Treat the OTV operation as low-frequency and cache issued certificates per candidate rather than re-requesting on each page view.

### How do I issue an OTV certificate through Jentic?

Install the SDK with pip install jentic, then search Jentic for 'Kerala PSC OTV certificate', load the schema for POST /otcer/certificate, and execute it with the candidate's PSC identifiers. Jentic injects the X-APISETU-APIKEY and X-APISETU-CLIENTID headers from your stored credentials. Run it through Jentic One, the self-hosted execution layer.

### Is the Kerala PSC API free to use?

API Setu is a Government of India service and the KPSC OTV endpoint is offered to onboarded integrators without per-call fees. You must complete the API Setu and DigiLocker partner onboarding to receive valid credentials.

### Does the OTV response include a verifiable signature?

Yes. POST /otcer/certificate returns a DigiLocker-compatible record signed at the issuing authority. Downstream consumers can treat the certificate as a verified government document rather than as untrusted JSON.

### Can I limit what my agent is allowed to do with the Kerala PSC API?

Yes. This API exposes a single operation, POST /otcer/certificate, and because you run Jentic One yourself, your own rules decide which operations and credentials the agent may use. You can add only the One Time Verification certificate call, so the agent can fetch OTV certificates and nothing else in the API Setu surface. Your API Setu API key and client id stay in your own instance and are injected at call time, never exposed to the agent.