Member Requests
For benefits software, ben-admin platforms, and HR solutions

The best way to manage constant change

See step-by-step why Noyo is the best way to automate member enrollment and eligibility.

wave

What if your team never had to touch an EDI file again? We've got good news.

Use API-powered workflows to manage all changes across carriers and lines of coverage.

Complete member changes within days, not weeks.

Monitor transactions in real-time and reconcile issues all in one place.

Only Noyo keeps data in sync, audits for issues, and confirms changes are processed correctly.

This is what hands-free automation looks like

Member changes are the heart and soul of Noyo. Instead of file-based workflows, benefits software platforms send member requests to Noyo’s API endpoints. Member requests represent the core operations you want to carry out on behalf of members (employees and dependents) at one or many carriers.
Noyo supports these types of member requests:

When you connect a group to a carrier through Noyo, the Noyo API automatically syncs and structures all member data for employees already enrolled in coverage. For existing employees, you’re all set to begin modifying coverage using the member request types above.

Every request is protected by Noyo’s unique ability to confirm transactions and proactively audit carrier data. Additionally, the real-time status of all member changes can be monitored in the Noyo dashboard.
Member Requests

Let’s look at a new hire enrollment request.
Here’s what the workflow looks like:

Member Requests Flowchart
Before you start: Create a new employee for a group and add dependents

When enrolling a new hire, first create a record of the new employee and their dependents within Noyo. For other member request types, go straight to step 1.

To get started, you’ll use the create an employee and create dependent endpoints.

This creates a standardized data object that contains personal information about the employee, as well as key employment details like hire_date, occupation, and employment_status. When an employee is created, Noyo will return a unique employee_id to reference when submitting a new hire enrollment request.

Step 1: Submit a new hire enrollment request

The new hire enrollment request makes it easy to add an existing employee, and optionally their dependents, to multiple lines of coverage across multiple carriers in a single API request.

Use the POST https://fulfillment.noyo.com/api/v1/employees/:employee_id/member_requests/new_hire endpoint to send Noyo unique identifiers for the employee, carriers, and plans for which you’d like to enroll. Optionally, you can also include details about plans an employee is waiving.

Noyo provides carrier ids and configuration details in advance, and we also make these details accessible via API. You have instant access to the most up to date group structure and plan eligibility info for each carrier.

Step 2: Noyo validates the member request and provides instant feedback

Noyo will immediately validate member requests, checking for duplicate records, missing fields, and any issues that could violate carrier-specific rules.

Step 3 & 4: Valid requests split into transactions and processed by carrier

When you submit a member request, you’re telling Noyo what successful enrollment looks like. Noyo then does the hard work of structuring the request into smaller transactions or action items that are carried out at the carrier.

For example, a New Hire Enrollment member request 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.

Step 5: Noyo continuously pulls information from the carrier to confirm success for every transaction

Part of the magic of Noyo is our ability to confirm that every transaction is completed exactly as expected. We call this round-trip confirmation. Noyo validates changes when they’re sent and then automatically checks the carrier’s system on the change’s effective date to confirm success – no other solution can do this.

Step 6: Poll the Noyo API to receive status updates

Poll the Noyo API to receive automatic status updates for each transaction, along with details on any issues that may arise. Transactions may be completed in mere seconds or longer, depending on the carrier and request type.

Real-time statuses of all transactions can be monitored in the Noyo dashboard. Alternatively, you can use Noyo’s API endpoints to create custom operational tooling.

Step 7: Noyo continuously syncs group information from carrier

Noyo proactively checks the carrier system for changes to member data for each managed group. This ensures that Noyo can capture any changes that might happen outside of Noyo (e.g., in a broker portal or directly at the carrier).

Our technology is setting the standard for what it means to truly keep data in sync.

Step 8: Noyo compares carrier data and programmatically identifies issues

When Noyo detects a change at the carrier, our Sync technology can automatically refresh data in our system to keep it up to date, as well as surface any discrepancies to platforms that may impact coverage.

We refer to this as programmatic issue detection, which solves a critical need in the industry to catch and resolve errors before they impact customers.

Step 9: Review any issues for fast reconciliation

Noyo instantly flags coverage-impacting issues to your team in the Noyo Reconciliation tool – resolve issues in a single click.

Before you start: Create a new employee for a group and add dependents

When enrolling a new hire, first create a record of the new employee and their dependents within Noyo. For other member request types, go straight to step 1.

To get started, you’ll use the create an employee and create dependent endpoints.

This creates a standardized data object that contains personal information about the employee, as well as key employment details like hire_date, occupation, and employment_status. When an employee is created, Noyo will return a unique employee_id to reference when submitting a new hire enrollment request.

Step 1: Submit a new hire enrollment request

The new hire enrollment request makes it easy to add an existing employee, and optionally their dependents, to multiple lines of coverage across multiple carriers in a single API request.

Use the POST https://fulfillment.noyo.com/api/v1/employees/:employee_id/member_requests/new_hire endpoint to send Noyo unique identifiers for the employee, carriers, and plans for which you’d like to enroll. Optionally, you can also include details about plans an employee is waiving.

Noyo provides carrier ids and configuration details in advance, and we also make these details accessible via API. You have instant access to the most up to date group structure and plan eligibility info for each carrier.

Step 2: Noyo validates the member request and provides instant feedback

Noyo will immediately validate member requests, checking for duplicate records, missing fields, and any issues that could violate carrier-specific rules.

Step 3 & 4: Valid requests split into transactions and processed by carrier

When you submit a member request, you’re telling Noyo what successful enrollment looks like. Noyo then does the hard work of structuring the request into smaller transactions or action items that are carried out at the carrier.

For example, a New Hire Enrollment member request 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.

Step 5: Noyo continuously pulls information from the carrier to confirm success for every transaction

Part of the magic of Noyo is our ability to confirm that every transaction is completed exactly as expected. We call this round-trip confirmation. Noyo validates changes when they’re sent and then automatically checks the carrier’s system on the change’s effective date to confirm success – no other solution can do this.

Step 6: Poll the Noyo API to receive status updates

Poll the Noyo API to receive automatic status updates for each transaction, along with details on any issues that may arise. Transactions may be completed in mere seconds or longer, depending on the carrier and request type.

Real-time statuses of all transactions can be monitored in the Noyo dashboard. Alternatively, you can use Noyo’s API endpoints to create custom operational tooling.

Step 7: Noyo continuously syncs group information from carrier

Noyo proactively checks the carrier system for changes to member data for each managed group. This ensures that Noyo can capture any changes that might happen outside of Noyo (e.g., in a broker portal or directly at the carrier).

Our technology is setting the standard for what it means to truly keep data in sync.

Step 8: Noyo compares carrier data and programmatically identifies issues

When Noyo detects a change at the carrier, our Sync technology can automatically refresh data in our system to keep it up to date, as well as surface any discrepancies to platforms that may impact coverage.

We refer to this as programmatic issue detection, which solves a critical need in the industry to catch and resolve errors before they impact customers.

Step 9: Review any issues for fast reconciliation

Noyo instantly flags coverage-impacting issues to your team in the Noyo Reconciliation tool – resolve issues in a single click.

Before you start: Create a new employee for a group and add dependents

When enrolling a new hire, first create a record of the new employee and their dependents within Noyo. For other member request types, go straight to step 1.

To get started, you’ll use the create an employee and create dependent endpoints.

This creates a standardized data object that contains personal information about the employee, as well as key employment details like hire_date, occupation, and employment_status. When an employee is created, Noyo will return a unique employee_id to reference when submitting a new hire enrollment request.

Step 1: Submit a new hire enrollment request

The new hire enrollment request makes it easy to add an existing employee, and optionally their dependents, to multiple lines of coverage across multiple carriers in a single API request.

Use the POST https://fulfillment.noyo.com/api/v1/employees/:employee_id/member_requests/new_hire endpoint to send Noyo unique identifiers for the employee, carriers, and plans for which you’d like to enroll. Optionally, you can also include details about plans an employee is waiving.

Noyo provides carrier ids and configuration details in advance, and we also make these details accessible via API. You have instant access to the most up to date group structure and plan eligibility info for each carrier.

Step 2: Noyo validates the member request and provides instant feedback

Noyo will immediately validate member requests, checking for duplicate records, missing fields, and any issues that could violate carrier-specific rules.

Step 3 & 4: Valid requests split into transactions and processed by carrier

When you submit a member request, you’re telling Noyo what successful enrollment looks like. Noyo then does the hard work of structuring the request into smaller transactions or action items that are carried out at the carrier.

For example, a New Hire Enrollment member request 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.

Step 5: Noyo continuously pulls information from the carrier to confirm success for every transaction

Part of the magic of Noyo is our ability to confirm that every transaction is completed exactly as expected. We call this round-trip confirmation. Noyo validates changes when they’re sent and then automatically checks the carrier’s system on the change’s effective date to confirm success – no other solution can do this.

Step 6: Poll the Noyo API to receive status updates

Poll the Noyo API to receive automatic status updates for each transaction, along with details on any issues that may arise. Transactions may be completed in mere seconds or longer, depending on the carrier and request type.

Real-time statuses of all transactions can be monitored in the Noyo dashboard. Alternatively, you can use Noyo’s API endpoints to create custom operational tooling.

Step 7: Noyo continuously syncs group information from carrier

Noyo proactively checks the carrier system for changes to member data for each managed group. This ensures that Noyo can capture any changes that might happen outside of Noyo (e.g., in a broker portal or directly at the carrier).

Our technology is setting the standard for what it means to truly keep data in sync.

Step 8: Noyo compares carrier data and programmatically identifies issues

When Noyo detects a change at the carrier, our Sync technology can automatically refresh data in our system to keep it up to date, as well as surface any discrepancies to platforms that may impact coverage.

We refer to this as programmatic issue detection, which solves a critical need in the industry to catch and resolve errors before they impact customers.

Step 9: Review any issues for fast reconciliation

Noyo instantly flags coverage-impacting issues to your team in the Noyo Reconciliation tool – resolve issues in a single click.