Cowin Gov Cin Co-WIN Certificate API

Name: Co-WIN Certificate API
Brand: Co-WIN Certificate API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentHealthcareEhr EmrapiKey, oauth21 EndpointsREST

For Agents

Download official Co-WIN COVID-19 vaccination certificates as PDF documents for verified beneficiaries in India. Use when an agent needs to retrieve a vaccination proof for compliance or onboarding.

Install Jentic One Beta

Connect the Co-WIN Certificate API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Co-WIN Certificate API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with Co-WIN Certificate API.

Download a COVID-19 vaccination certificate PDF for a verified beneficiary

Authenticate certificate retrieval through the DIVOC OAuth 2.0 authorization code flow

Provide an API key in the Authorization header for trusted backend integrations

GET STARTED

Start building with Co-WIN Certificate API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use Co-WIN Certificate API for, with concrete tasks.

★ HR Vaccination Compliance

An Indian enterprise's HR system collects Co-WIN vaccination certificates from new joiners during onboarding. The system calls POST /pdf/certificate with the beneficiary reference to fetch the official PDF and stores it against the employee record. This automates compliance evidence collection without forcing employees to email scanned copies.

Call POST /pdf/certificate with the beneficiary reference for new hire 'EMP-2026-0481' and store the returned PDF in the HRIS document store under their employee record.

Travel and Visa Documentation

Travel platforms and visa services that require proof of vaccination retrieve the Co-WIN certificate on behalf of the traveller after they consent through the DIVOC OAuth flow. The certificate is then attached to the visa application or travel booking. This avoids users uploading screenshots and ensures the document is the canonical signed PDF.

After the traveller completes the DIVOC OAuth flow, call POST /pdf/certificate and attach the returned certificate PDF to visa application 'VA-77821'.

Agent-Driven Compliance Workflow

An AI compliance agent embedded in an enterprise onboarding chat collects each new employee's beneficiary reference, then retrieves their Co-WIN certificate through Jentic. The agent files the PDF into the employee record and updates the compliance status flag without a human handling the document. Through Jentic, the agent finds the operation by intent and never holds the raw API key.

Search Jentic for 'download cowin vaccination certificate', execute POST /pdf/certificate with beneficiary 'BR-998877', and write the PDF response to the document vault.

Key Endpoints

1 endpoints — jentic publishes the only available openapi specification for co-win certificate api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

POST

/pdf/certificate

Download the vaccination certificate in PDF format

POST

/pdf/certificate

Download the vaccination certificate in PDF format

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Your Co-WIN credentials 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.

Intent-based discovery

Agents search Jentic by intent such as 'download a vaccination certificate PDF', and Jentic returns the matching Co-WIN operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

Time to first call

FAQs

Specific to using Co-WIN Certificate API through Jentic.

Why is there no official OpenAPI spec for Co-WIN Certificate API?

The Government of India does not publish a stand-alone OpenAPI specification for the Co-WIN certificate endpoint. Jentic generates and maintains this spec so that AI agents and developers can call Co-WIN Certificate API via structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer.

What authentication does the Co-WIN Certificate API use?

The endpoint accepts an API key in the Authorization header for trusted backend integrations, and an OAuth 2.0 authorization code flow against the DIVOC realm at https://divoc.cowin.gov.in for user-consented retrieval. Jentic stores either credential type encrypted in the vault.

Can I download a vaccination certificate for any beneficiary?

No. The endpoint requires either an authorized API key for the integrating organisation or explicit user consent through the DIVOC OAuth flow with the read:cert scope. Anonymous access is not supported.

How do I download a certificate through Jentic?

Search Jentic for 'download cowin vaccination certificate', load the POST /pdf/certificate schema, and execute with the beneficiary reference. The response is the binary PDF, which Jentic streams back to the agent.

What are the rate limits for the Co-WIN Certificate API?

The OpenAPI spec does not declare numeric rate limits. The Co-WIN portal enforces fair-use limits server-side. Production integrations should retry with exponential backoff on 429 responses and avoid bulk certificate downloads in tight loops.

Is the Co-WIN Certificate API free?

Access is granted by the Ministry of Health and Family Welfare to approved integrators at no cost, but you must complete the DIVOC partner registration to obtain credentials. The API itself does not charge per call.

Can I limit what my agent is allowed to do with the Co-WIN Certificate API?

Yes. Because you run Jentic One yourself, your own rules decide which operations and credentials the agent can use. The Co-WIN Certificate API exposes a single operation, the POST /pdf/certificate certificate download, so you scope the agent to just that call and nothing else is reachable unless you add it. The stored API key and DIVOC OAuth credentials are injected only at execution time, so the agent can fetch a certificate PDF without ever holding the raw credentials.