Member Transactions

Each member request (or snapshot) may contain multiple member transactions, which represent smaller sub-operations being carried out at carrier partners. For example, a single request that enrolls a new hire may result in two member transactions: one to add medical coverage at Carrier A, and a second to add dental and vision coverage at Carrier B. In most cases, it’s best to track the status of a member request or member snapshot, which is a combination of the statuses of individual transactions. A snapshot will not reach complete until all of the component transactions are complete. Noyo’s transaction endpoints allow partners to track transaction statuses if they choose.

​

Get Single Member Transaction

Returns the latest version of a single member transaction based on the ID provided.
Get Member Transaction

​

Get Member Transaction Status Details

Status Details are the processing history of a member transaction. This endpoint will return a list of all status details for a given transaction, as well as the event_created timestamp signifying when the transaction entered each status. The possible values for the status_detail field are detailed below. Returns a list of all status details for a given transaction.
Get Status Details

​

Get Member Transaction Status Details Response

This endpoint will return only the most recent status for a given transaction, with the event_created timestamp of when the transaction transitioned into this state.

​

Get Member Transaction Latest Status Detail

Returns the latest status detail for a given transaction.
Get Latest Status Detail

​

Get All Member Transactions

Returns a list of all member transactions
Get Member Transactions List

​

Verified Member Transactions

Often member transactions are sent in advance and will become effective at a date in the future (e.g, a new_hire member request with a hire_date of today, but the coverage does not start until the first of next month). Noyo works with carriers to verify that transactions have taken effect as expected and will mark the member transaction as verified when applicable. The verified field is the Unix time at which the member transaction was verified. You can expect the following timelines for verification at most carriers: Member transactions and snapshots in the completed status require no additional attention or action from you. Think of verified transactions as ones where we were able to do a successful double check that everything went as we expected.