​

Group connections

Create group connection to manage groups through the Noyo platform.

In the group_data object for the create endpoint, use Beam’s group number for the carrier_group_id. The format expected is a 7 character string, with two letters followed by 5 digits.

​

Sandbox testing

You may use the following special Beam group number carrier_group_ids in order to simulate different group connection statuses. If you use a group number listed below, the group connection will asynchronously update with the corresponding status within 10 seconds of submission. Only these three characters are evaluated to figure out the target status (e.g. 989 means noyo_review). Since group connections should be unique by a carrier ID and carrier group ID combination, you may use the final characters to iterate and test this interaction further.

​

Carrier configurations

Group, plan, and member configurations are where Noyo shares and receives details that are unique to a carrier. Every other part of Noyo’s payloads are standardized, but the configurations hold the unique fields and classifications that change from connection to connection. As part of preparing to connect to a new carrier, you need to understand the contents of each configuration and be sure your system is able to send the required data for each member.

​

Get the group configuration from Noyo

The Get carrier configuration by group list returns information about how the group is labeled and categorized within the carrier’s system. You can also see this data in the Command Center on a group’s detail page by clicking one of their carrier connections.

Groups that have Beam Benefits coverage will be configured with a group_number string, which is the primary group identifier with Beam Benefits.

{
    "group_id": "9ede6bc5-4fd3-459d-8741-70c3d4a9f652",
    "carrier_id": "9a0a7437-4097-4251-9e71-85384c0eb1c9",
    "configuration": {
        "group_number": "US00123"
    }
}

​

Get the plan configuration from Noyo

The details in Get group plan list should be used to map each Noyo plan to the corresponding plan in your own system. Importantly, each plan configuration has details about which populations are connected to an individual plan. Groups with multiple populations may link a plan with one or more of them.

{
    "plan": {
        "id": "ec158010-73c9-421c-86ec-5f4bfc92edeb",
        "version": "3c8ef5f5-031a-458d-9d7b-5f357ec2603f",
        "group_enrollment_id": "f64583d0-b89b-4e76-974e-c14673c693ea",
        "carrier_id": "9a0a7437-4097-4251-9e71-85384c0eb1c9",
        "line_of_coverage": "life",
        "name": "life",
        "code": "",
        "plan_type": "basic",
        "effective_start_date": "2023-01-01",
        "effective_end_date": "9999-12-31",
        "status": "active",
        "eligible_member_types": ["all"],
        "waiting_periods": [
            {
                "waiting_period_enrollment_type": "new_member",
                "waiting_period_rule": "hire_date"
            },
            {
                "waiting_period_unit": "day",
                "waiting_period_enrollment_type": "current_member",
                "waiting_period_amount": 0,
                "waiting_period_rule": "after_waiting_period"
            }
        ],
        "termination_policy": "last_work_date",
        "volume_rules": {
            "volume_rule_type": "member_type_fixed_volume",
            "member_volumes": [
                {
                    "member_type": "spouse",
                    "volume": 2000
                },
                {
                    "member_type": "domestic-partner",
                    "volume": 3000
                },
                {
                    "member_type": "child",
                    "volume": 1000,
                    "member_conditions": {
                        "maximum_age": {
                            "value": 6,
                            "unit": "months"
                        }
                    }
                },
                {
                    "member_type": "child",
                    "volume": 1500,
                    "member_conditions": {
                        "minimum_age": {
                            "value": 6,
                            "unit": "months"
                        }
                    }
                }
            ]
        },
        "plan_configuration": {},
        "created": 1695918911,
        "modified": 1705423256,
        "dependent_child_age_limits": [],
        "cobra_rules": {}
    },
    "ge": {
        "id": "f64583d0-b89b-4e76-974e-c14673c693ea",
        "version": "8bb64e76-640e-4fe1-9455-6beeaeb8d043",
        "group_id": "f91701f3-3646-431a-ba0a-053a9c471d52",
        "carrier_id": "9a0a7437-4097-4251-9e71-85384c0eb1c9",
        "line_of_coverage": "life",
        "status": "active",
        "open_enrollment_start_date": "2022-12-01",
        "open_enrollment_end_date": "2022-12-31",
        "open_enrollment_renewal_date": "2023-01-01",
        "effective_start_date": "2023-01-01",
        "effective_end_date": "9999-12-31",
        "created": 1695918911,
        "modified": 1705423256
    }
}

​

Send the member configuration to Noyo

Each member snapshot sent to Noyo can contain a configuration section. Depending on each carrier’s requirements, you may need to use this section to include carrier-specific identifiers like classes, subdivisions, or bill groups. These go in the coverage block’s carrier_config section and ensure that members are enrolled in the correct coverages.

Requests to enroll in Beam Benefits coverage do not require a carrier_config block.

​

Carrier-specific behaviors

• Coverage effective and termination dates cannot be modified through Noyo. If you need to change an existing effective/termination date, reach out to Beam directly. We will automatically sync these changes into our system.
• Beam requires an SSN for all employees attempting to enroll in coverage, while dependent SSNs are optional.
• Requests that include Beam coverage for multiple dependents with identical SSNs will be rejected.
• Dependents cannot be enrolled simultaneously under multiple employees in the same group.
• When adding voluntary life and/or critical illness coverage, you must send a volume amount for each.
• Beam requires event reasons for all requests. If an event reason is not provided, processing is subject to failure or delay. We recommend sending event reasons at all times.
• It’s best practice to submit email addresses for all members upon initial enrollment (failure to do so will cause the member to have to self-register with Beam). However, Beam will not accept email address and phone number changes through Noyo after a new hire enrollment has been processed. Members must make these changes directly with Beam via the app, the website, or customer support.

​

Connection Basics

​

Getting groups connected

To connect a new or existing group, first send an email to edi@beambenefits.com that includes the group’s name, group number, and a note that the group will be managed through Noyo. Beam will confirm receipt within two business days.

At that point, you can request a group connection with the group name and group number (as outlined in the Technical Spec). As with all other Sync carriers, we process a group connection by pulling all plan, member, and group structure data from Beam to populate our system.

If at any point we encounter an issue connecting the group, Noyo will work with Beam to resolve the issue. We may contact you if your input is needed, and these group connections may take longer to complete.

​

Groups are considered fully connected when:

• Noyo returns get group connection as “completed.”
• You’ve linked Noyo’s IDs for account structure information, plans, members, and coverages to your own, and established an account structure mapping process.
• You’ve deactivated previous forms of data exchange and are ready to send all enrollment changes through Noyo.

​

Processing member changes

Each member change is broken into one or more individual “transactions. Our integrations with API-enabled Sync carriers generally result in 90% of member transactions arriving at the carrier within 10 minutes of being sent to Noyo, and 95% of transactions being confirmed by Noyo within 4 business days of original receipt.

​

Round-trip confirmation

As with other Sync carriers, Noyo is able to read data directly from Beam s system. Noyo monitors each transaction with round-trip confirmation, which triggers a check in the carrier’s system after the change is sent and again on the change’s effective date to ensure that enrollments go through as expected.

Use the Tracking API to see the results of round-trip confirmation and get a granular view of how each change is being processed.

​

Managed changes

Our goal is to confirm all member changes within 4 business days. However, some transactions cannot be confirmed automatically after being submitted through our API because special handling is required. We call these “managed” transactions and they may have longer confirmation timelines.

Types of managed changes:

• Date of hire changes Adjusting the date of hire after it has been set.
• Reinstatements Reinstating previously terminated members or members that have removed all coverage.
• Aging out Enrollments for dependents who are not yet 26 but will turn 26 within 90 days of the day the change was created.

​

Retroactive changes

Beam considers requests with an effective date of more than 60 days prior a retroactive change. These must be manually reviewed by Beam and can have a turnaround time of 5-10 days for completion.

Beam will not update an effective date to be more than 60 days prior to when the change was sent, which can sometimes result in effective date mismatches.

​

Other scenarios

• If a group offers basic life and AD&D, those coverages are issued to all non-terminated members of the group (even if a member has waived all other coverages).

​

Open enrollment

You can send the group’s plan-level renewal decisions to Noyo once they’ve been officially communicated to Beam. Noyo will check Beam’s system daily until the new plans are available to ensure that they are installed correctly.

When the plans in Beam’s system match the expectations you submitted, the get renewal decisions will move to “ready” and you will be able to send member requests with each member’s open enrollment elections for the new plan year.

Beam’s OE windows are the first of the month prior to the 16th of the OE month. For example, for a 3/1 OE, the OE window would be 2/1 to 3/16. Any enrollments outside of the OE window need to be sent to Beam directly. There are no blackout periods.