API: Requests COBRA: Not supported Geographies: All Group Size: All Lines: add, critical, dental, hospital, life, ltd, std, vision Name: Unum Network: Sync New Group Connection Time: 5–10 days Unsupported: -

​
Group connections

Create a group connection request to manage groups through the Noyo platform. In the group_data object for the create endpoint, use either the master agreement number or the Unum policy ID as the ****carrier_group_id.
  • For ****master agreement number, the format expected is an alphanumeric string of flexible length (often 19-21 characters).
  • For policy ID, the format expected is a numerical string of 8 characters. If a policy ID is fewer than 8 characters, add leading zeroes. For example, “123456” becomes “00123456”.
Some groups may have multiple policy IDs under a single master agreement number. Any request for a single policy ID will result in a single group configuration, containing all policy IDs associated with that master agreement number.

​
Sandbox testing

You may use the following special Unum policy ID as the carrier_group_id in order to simulate different group connection statuses. If you use a policy ID listed below, the group connection will asynchronously update with the corresponding status within 10 seconds of submission. Only the first three digits 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.
Test ID PatternResulting Status
989***noyo_review
767***waiting_on_carrier
545***action_required
323***unable_to_connect
212***carrier_authorization

​
Carrier configurations

Dynamic config is recommended for all new Noyo integrations and makes carrier-specific config values no longer required.
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 group carrier configuration endpoint 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 Unum coverage will be configured with a master_agreement_number string, which is the primary group identifier with Unum, along with a list of one or more division_ids, ****eligibility_classes, and policy_ids to categorize employees enrolling in coverage. 
{
    "group_id": "ab42a162-2ad8-429c-b82e-fb3757ae693e",
    "carrier_id": "23054cd9-0a41-43e3-bd43-2d2138006536",
    "configuration": {
        "master_agreement_number": "H562343085C02814123",
        "division_ids": ["0001", "0002"],
        "eligibility_classes": [
            {
                "eligibility_class_code": "001",
                "eligibility_class_description": "All Salaried Employees"
            },
            {
                "eligibility_class_code": "001",
                "eligibility_class_description": "All Hourly Employees"
            }
        ],
        "policy_ids": ["00123456", "00654321"]
    }
}

​
Get the plan configuration from Noyo

The details in the plan configuration 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": "00cc9a6a-3a7a-4b3a-b8aa-58fa99caf0ff",
        "version": "787df63a-7d92-40ba-8f4e-ba762e75c8a0",
        "group_enrollment_id": "29edfe24-c69b-4d68-b5a8-0f6e29f14fce",
        "carrier_id": "23054cd9-0a41-43e3-bd43-2d2138006536",
        "line_of_coverage": "dental",
        "name": "dental",
        "code": "",
        "effective_start_date": "2023-01-01",
        "effective_end_date": "9999-12-31",
        "plan_type": "ppo",
        "network": "",
        "voluntary": false,
        "status": "active",
        "eligible_member_types": ["all"],
        "waiting_periods": [
            {
                "waiting_period_rule": "hire_date",
                "waiting_period_enrollment_type": "new_member"
            },
            {
                "waiting_period_unit": "day",
                "waiting_period_rule": "after_waiting_period",
                "waiting_period_amount": 0,
                "waiting_period_enrollment_type": "current_member"
            }
        ],
        "termination_policy": "last_work_date",
        "cobra_rules": {
            "eligible": false
        },
        "created": 1695919211,
        "modified": 1705423193,
        "plan_configuration": {
            "eligibility_class_codes": ["001"],
            "policy_ids": ["00123456"],
            "division_ids": ["0001", "0701"]
        },
        "dependent_child_age_limits": []
    },
    "ge": {
        "id": "29edfe24-c69b-4d68-b5a8-0f6e29f14fce",
        "version": "ef8d495b-1300-4ea9-8bdb-ff54df6a2969",
        "group_id": "029bf935-9251-41d1-a102-3ece2121920f",
        "carrier_id": "23054cd9-0a41-43e3-bd43-2d2138006536",
        "line_of_coverage": "dental",
        "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": 1695919211,
        "modified": 1705423193
    }
}

​
Send the member configuration to Noyo

Each member request 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. Member requests to enroll in Unum coverage may include optional division_id, optional eligibility_class_code, and optional policy_ids matching the corresponding values in the group plan configuration, respectively. The policy_ids object is a mapping from the Noyo plan IDs to the Unum policy IDs, grouped by the plan’s Line of Coverage. If the caller omits any of these values, Noyo will attempt to resolve the correct values in cases where only one option is available for the member. Noyo will reject the request if the information provided isn’t enough to resolve to a single plan. 
{
    "division_id": "0001",
    "eligibility_class_code": "001",
    "policy_ids": {
        "dental": {
            "e2e3cd33-c920-43b8-9601-1a6d3a77bd4c": "00123456"
        }
    }
}

​
Carrier-specific validations

None.

​
Carrier-specific behaviors

Unum does not prevent open enrollment transactions from being sent at any time of the year, so Noyo sets open_enrollment_end_dates to 9999-12-31. Depending on their internal logic, Unum may apply the transaction or not - Noyo will monitor each transaction. Unum does not expose volume rules for any plans, and so Noyo will accept any volume amount submitted by the platform. Noyo will return the amount assigned to the member by Unum. If EOI is required, the member will be contacted directly. Unum does not allow automatic changes to first_name ****or date_of_birth for dependents. Noyo will resolve these changes manually, but a longer SLA will apply (up to 10 days in some cases).

​
EOI

Evidence of insurability (EOI) may be required for Voluntary Life coverages.