Skip to main content

Participant registry

Every NHCX API call, whether a registry lookup, a certificate fetch or a claim submission, is rejected unless it carries a valid Bearer token, so this is the first call any integration makes and...

Calls

CallMethod and pathWhat it does
Get session tokenPOST /get/sessionExchanges the participant's client_id and client_secret (OAuth 2.0 client credentials) for a Bearer access_token valid for 1200 seconds.
Participant update (v1)POST /participant/updateUpdates a participant's registry record; participant_code and roles are mandatory, every other field (certificate, endpoint, contacts, status) is optional.
Participant certificate and bridge update (v2)POST /v2/participant/updateStages a change to a participant encryption certificate and/or endpoint URL; returns a transactionid for passcode confirmation via /update/validate.
Participant searchPOST /participant/searchReads a participant's full registry record by participant_code, including roles, status, encryption_cert and endpoint_url.
Participant details (v2 search)POST /participant/detailsV2 variant of participant search: takes participant_code and returns the matching full registry records.
Fetch participants listPOST /fetch/participants/listPayer discovery: lists participants filtered by role, registration date window and optional entity type; the first step of the cashless workflow.
Fetch certificatePOST /fetch/certsReturns a participant's public encryption certificate (PEM X.509 or SPKI key) by participantid; cache it for 24 hours and use it to build the JWE.
Fetch certificate pathPOST /fetch/certs/pathCompanion to /fetch/certs: takes the same participantid body and returns a string described as the participant's certificate path.
Update certificate (v2, no passcode)POST /v2/update/certReplaces a participant's public encryption certificate by participantId without passcode validation; the same schema is echoed back on success.
Get linked registry master (internal)POST /get/linked/registry/mstInternal-use participant-service operation that fetches the linked registry master; listed in the OpenAPI but not intended for integrators.
Link ABHA number to policiesPOST /participant/link/abha/policyPayer-side write that links a beneficiary's ABHA number and member id to one or more products, so provider policy lookups can find them.
Link ABHA number to policies (V2)POST /V2/participant/link/abha/policyV2 variant of the ABHA policy link; same ParticipantLinkAbhaRequest body and ParticipantLinkAbhaResponse as the unversioned call.
Initiate ABHA policy link (v2)POST /v2/participant/link/abha/policy/initFirst half of the two-step v2 link: submits the ABHA policy link request, to be confirmed with a passcode via the validate endpoint.
Validate ABHA policy link (v2)GET /v2/participant/link/abha/policy/validateSecond half of the two-step v2 link: confirms an initiated ABHA policy link with the passcode and transactionId query parameters.
De-link ABHA policiesPOST /participant/delink/abha/policyRemoves specific products from a member's policy link for a payer, keyed on payerid, memberid and the products listed.
De-link ABHA policies (V2)POST /V2/participant/delink/abha/policyV2 variant of the ABHA policy de-link; same ParticipantDeLinkAbhaRequest body and response as the unversioned call.
Get beneficiary policiesPOST /participant/get/policiesLooks up the policies linked to a beneficiary by ABHA number, member id or mobile number, returning the payer and product details needed for claims.
Get beneficiary policies (V2)POST /V2/participant/get/policiesV2 variant of the beneficiary policy lookup; same FetchParticipantPoliciesRequest body and ParticipantListResponse as the unversioned call.
Update ABHA numberPOST /update/abhanumberReplaces a placeholder (dummy) ABHA number with the beneficiary's real ABHA number in the ABHA_AUTH_TRANSACTION table.
Link payer productPOST /product/linkRegisters a product (product id and name) against a payer's participant code, so that it can be referenced in ABHA policy links.
De-link payer productPOST /product/delinkRemoves a product (product id and name) from a payer's participant code in the registry.
Get product ownerPOST /product/getownerResolves a product id to the participant code of the payer that owns it.
Get product id and namePOST /participant/getProductIdNameRetrieving API described as generating the product id and product name; declared with a bare string request body and a participant-code response.

Base URLs

EnvironmentBase URL
Sandbox, Participant service.https://apisbx.abdm.gov.in/pmjay/sbxhcx/participanthcxservice
Production.https://apisprod.nha.gov.in/pmjay/hcx/participanthcxservice

Guides that use these calls

The whole specification, with a request you can send from the page, is the Participant registry API reference.