NDHM (Ayushman Bharat Digital Mission) APIs for AI Agents
HealthcareEhr EmrJentic-Generated SpecsNo authAgent Ready
NDHM (Ayushman Bharat Digital Mission) API Catalog
5 APIs across 1 product group. All share one credential.
Healthcare5
NDHM Health ID ServiceIssue and manage ABHA Health IDs with Aadhaar or mobile-based registration, KYC, profile updates, password recovery, and Health ID card generation.~73 endpointsNDHM GatewayRoute consent requests, care-context discovery, and health-data flows between Indian Consent Managers, Health Information Providers, and Health Information Users on the NDHM network.~48 endpointsNDHM HIU SpecificationsImplement the HIU role in the NDHM network - initiating consent requests, receiving encrypted health-information bundles, and responding to Gateway callbacks.~32 endpointsNDHM HIP SpecificationsImplement the HIP role in the NDHM network - handling care-context discovery, link confirmations, consent notifications, and encrypted health-information transfers.~30 endpointsNDHM Health Data Consent ManagerBuild a patient-facing Consent Manager that aggregates Indian health data across HIPs and shares it with HIUs based on explicit consent.~22 endpoints
Which NDHM (Ayushman Bharat Digital Mission) API should I use?
| I want to... | Use | Why |
|---|---|---|
| Create or look up a patient's ABHA Health ID | NDHM Health ID Service | The Health ID Service handles Aadhaar and mobile-OTP registration, KYC, profile updates, and card generation; the other four use the ABHA it issues but do not create it. |
| Orchestrate consent and data flows across all roles | NDHM Gateway | The Gateway is the central router that broadcasts discovery, consent, and data-flow messages between CMs, HIPs, and HIUs; use it when you need cross-role coordination rather than one participant's endpoints. |
| Build the app that requests and consumes patient records | NDHM HIU Specifications | The HIU specification bundles the consumer-side operations that initiate consent requests and receive encrypted bundles, distinct from the provider that serves the data. |
| Serve patient records as a provider | NDHM HIP Specifications | The HIP specification bundles the provider-side discovery, linking, consent-notification, and encrypted-transfer callbacks a record-holding hospital must implement. |
| Run the patient-facing consent aggregator | NDHM Health Data Consent Manager | The Consent Manager holds consent records and presents the patient UI for grant and revocation; the Gateway routes to it but does not itself store consent or show the patient interface. |
Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Standing up NDHM by hand means signing JWTs, managing separate client credentials for the Health ID Service and each Gateway-facing role, and handling asynchronous discovery, consent, and data-flow callbacks yourself. Through Jentic you install once, import the NDHM specifications you need from the Jentic API Directory, store the credentials once, and your agent calls them.
Permission scoping
NDHM operations carry Health IDs, consent ids, and care-context links in the signed request body rather than the URL path, so you scope the agent to the operations it needs per role. Because you pick that operation set, sensitive calls such as profile deletion, consent revocation, or health-information transfer stay unavailable unless you add them.
Credential isolation
FAQs
Specific to using NDHM (Ayushman Bharat Digital Mission) APIs through Jentic.
What is NDHM and how do its APIs fit together?
NDHM, now the Ayushman Bharat Digital Mission, is India's national health-data network. The Health ID Service issues the ABHA identifier for each patient, the Gateway routes messages between roles, the HIP and HIU specifications define the provider and consumer sides of record exchange, and the Consent Manager holds consent records and the patient-facing UI. Together they cover identity, consent, and consented data transfer.
Does one credential work across all five NDHM APIs?
No. The Health ID Service uses a bearer JWT from its own OTP-based login, while the Gateway, HIP, HIU, and Consent Manager specs use signed JWTs issued through the Gateway and validated against its certificate endpoint. Participants share the Gateway trust model but each hold their own signing keys and client credentials.
Why does Jentic publish these specs instead of NDHM?
NDHM does not publish maintained OpenAPI specifications for these services, offering only reference documentation and a deprecated third-party import. Jentic generates and maintains all five specs, validates them against the live sandbox, and keeps them current so agents and developers can call them through structured tooling.
BOOK A DEMO
Start Connecting APIs to Your AI Agents
Browse thousands of APIs and connect them all to your agent with Jentic One. One layer, one credential — every API your agent needs.
