1
Send Snapshot
First, send a snapshot to Noyo:You’ll receive the ID of the created snapshot:If you use webhooks, you’ll receive
Request
Response
difference.created
events for every change or update in the snapshot.2
Retrieve differences
We then call the tracking endpoint to retrieve a field-level list of differences associated with the snapshot. These differences will either be pending changes introduced by the snapshot, or discrepancies raised during round-trip confirmation. They can be pulled at any time and will always reflect their real-time status.For this example, we’ll assume your snapshot included one new item– enrolling a dependent in vision coverage.Call the differences endpoint using the snapshot ID as a query parameter:The response returns one difference (pending change)– the carrier doesn’t have an enrollment in the snapshot (that’s what is being processed)
Request
Response
3
Track over time
Fast forward a day or two. The carrier has enrolled the dependent successfully, but with a later effective date due to their rules and limitations. The tracking endpoint will surface this information. Let’s call it again:We now get an updated response. The original difference is now marked as resolved, meaning the carrier successfully enrolled the dependent. There’s a new discrepancy raised noting the difference in effective start date. (some payload fields omitted for brevity)
Request
Response
- For the dependent enrollment, a
difference.resolved
event (in addition to the original creation event) - For the effective date discrepancy, both a
difference.created
anddifference.discrepancy
event - For the snapshot, both a
member_snapshot.status_change
event and amember_snapshot_carrier_fulfillment_status.status_change
event