What’s happening behind the scenes when you send a snapshot
Create and send a member snapshot
POST /api/v1/groups/:group_id/member_snapshots
.Populate the Employee section with your custom_individual_id
and the employee’s classifications. Set the Employment information and Employment Dates. Send as much demographic information as possible in the Person and Dependent sections.Populate the Coverages list by adding a block for each plan or coverage the member and their dependent(s) should be enrolled in:line_of_coverage
and plan_id
to the linked Noyo plancarrier_config
block to the member’s chosen account structure option(s) (this section may be blank, or be populated according to individual carrier requirements)individual_type
and custom_individual_id
to match your employee recordeffective_start_date
and effective_end_date
of the coverage. (If a user hasn’t requested to terminate coverage, use datemax of 9999-12-31 for the end date.)event_id
, reason, and date for the relevant event.With this data, a member snapshot should be ready to send. Check out our special cases documentation for specific examples of how to formulate a member snapshot for different scenarios:If successful, you should get a response with a new unique ID for the snapshot, the original contents of the snapshot, and an initial status of submitted
. Your system should record the new snapshot ID to check on the status (see below).A more specific breakdown of the snapshot format can be found in the API Reference.Noyo validates snapshot content
Changes identified and queued
Carrier processes changes
Noyo confirms that the change was made (sync carriers)
completed
in our system.Check the status of submitted snapshots
processing
)completed
)canceled
)replaced
)complete
. If any transactions had an effective date in the future, our second round-trip confirmation check validates the data with the carrier again on that date.processing
until the file is sent, when it moves to completed
.Get updated member data on demand and manage discrepancies