Use the Eligibility V3 API

API endpoints, ASC X12 EDI Support, and using our Postman collection.



The JSON attributes in our APIs use snake-case, with the first letter of the attribute in lower case as in tradingPartnerServiceId. Our APIs are case-sensitive and your JSON request body must observe this convention.

Eligibility sandbox endpoint

Eligibility production endpoint



The production endpoint queries to determine patient eligibility through an X12 270 request. It formats the request in JSON for an Eligibility status HTTP query for a patient. It receives an EDI 271 response, which is translated to JSON as the response body. It makes this popular EDI transaction more accessible to developers and to users’ applications. We manage the X12 standards in the background and give you efficient access to medical subscriber or dependent plan membership, copays, co-insurances, deductibles, and more, in an easy-to-use and human-readable format.

Eligibility endpoints components



Request Method


Bearer Token


API endpoint


Raw-X12 endpoint


API Healthcheck


Operation Mode

Real-time, one request





API components

API Components


Content-Type Header

Always defaults to application/json

Authorization Header

Pass the Bearer authorization token to authorization header

grant_type Field

Always client_credentials

X12 EDI support

We support a dedicated X12-formatted Eligibility API to send your submission in X12 EDI format. It supports the standard syntax for a complete X12 EDI 270 transaction set.

Postman Collection

Try our Postman collection!
Run in PostmanRun in Postman

OpenAPI specification

Download our OpenAPI 3.0 Spec.

Using ConnectCenter Payer values in the API

You obtain Payer ID values from the Legacy Change Healthcare (LCHC) payer list. The payer list is searchable by payer name or by their serviceId. The serviceId is the searchable numeric 5-digit ID value associated with each service provided by the listed payer.

Did this page help you?