This section walks you through the complete member change workflow: creating the snapshot, getting snapshots, processing, and checking status.
Submit a snapshot for an employee and their family using
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
plan_idto the linked Noyo plan
- Set the
carrier_configblock to the member’s chosen account structure option(s) (this section may be blank, or be populated according to individual carrier requirements)
- Set the
custom_individual_idto match your employee record
- Set the
effective_end_dateof 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.
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.
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.
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.
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.
Updated 29 days ago