Member Snapshots integration. Exposes endpoints for submitting member enrollment snapshots and polling the processing job status.
Ingest member snapshots
Accepts a trading partner member snapshot batch and returns a snapshot identifier.
Headers
x-api-keyThe x-api-key header is used to authenticate with the API using your API key. Value is of the format YOUR_KEY_HERE.
Ingest member snapshots › Request Body
Company payload. Identifies the company the enrollment belongs to.
enrollment_actionEnrollment action type (new_enrollment, change, or termination).
Employee payload.
Coverage payload.
Managing third party payload. Identifies the party that collected and manages the enrollment when it is not the submitting trading partner.
Optional dependents payload array.
Optional events payload array.
Ingest member snapshots › Responses
OK
snapshot_idExternal snapshot identifier for status polling.
Per-item results for all submitted items.
Poll snapshot processing status
Returns the current status for a submitted member snapshot. Poll this endpoint with the snapshot_id returned from POST /member-snapshots until status is complete or error.
path Parameters
snapshot_idHeaders
x-api-keyThe x-api-key header is used to authenticate with the API using your API key. Value is of the format YOUR_KEY_HERE.
Poll snapshot processing status › Responses
OK
snapshot_idSnapshot identifier returned from submission.
statusExternal processing status (pending, processing, complete, error).
Item-level outcomes for transactions in the submitted snapshot payload.
Dry-run member snapshots
Validates and simulates a member snapshot batch without persisting, queueing, or transmitting anything. Each item runs through the same validation gates and carrier pipeline as a real submission, with carrier calls mocked for success, and the response reports the outcome each item would reach. A dry run confirms a submission passes validation and that every carrier request is constructible from the data; it cannot predict whether the real carrier would accept it.
Headers
x-api-keyThe x-api-key header is used to authenticate with the API using your API key. Value is of the format YOUR_KEY_HERE.
Dry-run member snapshots › Responses
OK
Per-item dry-run outcomes, one per submitted snapshot item.