The Member Change Workflow

What's happening behind the scenes when you send a snapshot

This section walks you through the complete member change workflow: creating the snapshot, getting snapshots, processing, and checking status.

Step 1: Create and send a member snapshot

Submit a snapshot for an employee and their family using 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:

  • Set the line_of_coverage and plan_id to the linked Noyo plan
  • Set the carrier_config block to the member’s chosen account structure option(s) (this section may be blank, or be populated according to individual carrier requirements)
  • Set the individual_type and custom_individual_id to match your employee record
  • Set the effective_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.)

Populate the Events section with the event_id, reason, and date for the relevant event.

With this data, a member snapshot should be ready to send. 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 processing. 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.

Steps 2-3: Noyo sends changes to the carrier

Noyo validates the request for content and to be sure it has a chance to be processed by the carrier. For full detail on possible responses, see Snapshot Responses.

Noyo will process the snapshot contents, break the snapshot into transactions, generate the correct payload to each target carrier, and check for a response that the transmission was successful. We’ll immediately try to read back from the carrier to see that their data has been updated to match our request. This is the first step of our round-trip confirmation process to ensure that member data is accurate across systems.

4-5: Noyo continuously pulls information from the carrier to confirm success

For each transaction sent via Noyo, we confirm that every detail is completed as expected. Noyo's round-trip confirmation functionality validates changes when they’re sent and then automatically checks the carrier’s system to confirm success on the change's effective date.

6: Check the status of submitted snapshots

At any time after a snapshot has been accepted, you can poll Noyo's snapshot endpoints for the status of each request. See Snapshot Status for full details.

7-9: Get the most up-to-date member details

As soon as the carrier has made the requested changes, Noyo updates our system to reflect the new data. This will happen at the same time the snapshot status reaches complete. At this point, it's possible to use our member data endpoints to pull back the latest info into your own system. If desired, you can use this data for reconciliation, or to support your own internal tooling.

What’s Next

Get details about possible responses to snapshot requests