Skip to main content
POST
Coordinate benefits across payers

Authorizations

Authorization
string
header
required

Service (M2M) access token issued by POST /auth/token using the client_credentials grant. Required scopes, where known, are listed on each operation below.

Scopes

eligibility:write

Body

application/json
subscriber
object
required

The policyholder, or a dependent who holds their own member id. At least one of member_id or ssn is required.

payer_id
string
required

The payer you already know the patient has, and the payer that is asked. Find it with GET /payers. Aliases and mixed case both resolve; surrounding whitespace is trimmed before the id is sent.

Example:

"60054"

date_of_service
string

Calendar date (YYYY-MM-DD) or a full ISO datetime; defaults to today. A future date is accepted, for a scheduled visit; a date more than two years old is a 400.

Example:

"2026-08-10"

dependent
object

Send this only for a patient covered under someone else's policy who has no member identifier of their own — and then subscriber must carry the policyholder, not the patient.

A dependent who does hold their own member identifier goes in subscriber instead and this object is omitted. Getting the two the wrong way round produces a payer rejection rather than a wrong answer.

Two dependents on one policy are two different questions, and are never served one another's answer.

Response

The check completed. A payer rejection is also a completed check and answers 200, not a 4xx.

data
object
required

The payer's coordination verdict. There is no verdict field of ours, no coverages array and no recommendation: read coordination_of_benefits.classification and coordination_details.

A rejection and an answer are two shapes. A rejection reports status and status_reason and nothing about coverage; an answer reports the verdict and its detail and carries no status.

request_id
string
required
Example:

"c1a7f3e2-5b9d-4a68-9f21-7d3c4b6e8a05"