Jentic publishes the only available OpenAPI specification for Gateway, keeping it validated and agent-ready. The NDHM Gateway is the central hub of India's National Digital Health Mission that routes interactions between Consent Managers (CMs), Health Information Providers (HIPs), and Health Information Users (HIUs). The 48-endpoint surface covers care-context discovery, account linking, consent flows, health-data flow, identification, and monitoring — split across CM-facing, HIP-facing, and HIU-facing roles. Authorisation uses signed JWTs distributed via the Gateway's openid-configuration and certs endpoints.
48 endpointsJentic publishes the only available OpenAPI specification for Gateway, keeping it validated and agent-ready. The NDHM Gateway is the central routing hub of India's National Digital Health Mission, brokering interactions between Consent Managers, Health Information Providers, and Health Information Users. It exposes 48 endpoints grouped into discovery, link, consent flow, data flow, monitoring, and session management, plus the well-known OpenID configuration and JWT signing certificate endpoints. Participants register with the Gateway and call its APIs to find each other, raise consent, and exchange encrypted health records under the NDHM 0.5 specification.
48 endpointsStep 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 | shStep 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 instanceJentic 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.
Jentic publishes the only available OpenAPI specification for Health Data Consent Manager, keeping it validated and agent-ready. The Health Data Consent Manager (CM) is the patient-facing component of India's NDHM that aggregates health information across Health Information Providers and shares it with Health Information Users based on the patient's explicit consent. The 22-endpoint surface covers care-context discovery responses, consent request initiation and fetching, health-information request handling, link confirmation, and heartbeat monitoring.