Poll until status is no longer pending or processing. A completed status does not guarantee all members succeeded — always check individual code values.
carrier_application_id is the carrier's own reference for the member's application (an Oscar application id, an Anthem ACN, and so on). It is null until the carrier issues one and is returned whether or not the transmission succeeded, so it is the number to quote when contacting the carrier.
3. Check Current Coverage
GET /api-integrations/ichrax/v1/coverage/{partner_individual_id} with the subscriber's partner_individual_id to see the coverage their family holds on a date:
Code
GET /api-integrations/ichrax/v1/coverage/EMP-001?as_of=2026-09-03x-api-key: your-api-key-here
The response groups the family's coverage by plan. Each plan lists every covered member with their own coverage dates:
as_of defaults to today. Pass a future date to confirm an enrollment that has not started yet, for example as_of=2027-01-01 during open enrollment. The id in the path must be the subscriber's; a dependent's id returns 404. A subscriber whose coverage has all ended before as_of returns 200 with an empty coverages array, while a subscriber with no recorded coverage at all returns 404.
carrier_membership_id and carrier_application_id are the carrier's own identifiers for the enrollment, and they sit on the coverage rather than on each member: one membership covers the subscriber and every dependent under it. carrier_application_id names the application that established the coverage in force on as_of, so a mid-year change that reopens the coverage reports that change's application rather than the original one. Both are null when the carrier does not issue that identifier, or when the coverage was recorded before the carrier returned it, so treat null as normal rather than as an error.
Per-Member Status Codes
Code
Meaning
200
Member processed successfully
207
Partial success — review messages
400
Validation failure — member not submitted
500
Internal error processing this member
Adding Dependents
Include a dependents array alongside the employee. Dependents must also be listed in coverage_members within the coverage record.
A complete new_enrollment snapshot exercising every optional section — person contact and details, employment, PCP and prior coverage, agent, agency, payment, and carrier-specific config. coverage_members[].event_id references an entry in the top-level events array.