> ## Documentation Index > Fetch the complete documentation index at: https://docs.noyo.com/llms.txt > Use this file to discover all available pages before exploring further. # Delta Dental Northeast > Technical documentation for integrating with Delta Dental Northeast through Noyo | | | | - | - | | **API** | Snapshot | | **COBRA** | Supported | | **Geographies** | All | | **Group Size** | Confirm with carrier | | **Lines** | Dental, vision | | **Name** | Northeast Delta Dental | | **Network** | Send | | **New Group Connection Time** | 6-8 weeks | | **Noyo ID** | `6ecb26f1-da0f-40b3-9e9a-3272aa17d70e` | ## Group connections [Create a group connection request](/docs/groups/connections/request-a-group-connection) to manage groups through Noyo. In the `group_data` object for the create endpoint, use the Northeast Delta Dental group ID (also called the master agreement number) for the `carrier_group_id`. ### Sandbox testing Use the following special Northeast Delta Dental `carrier_group_id`s to simulate different group connection statuses. Test group connections with these IDs will asynchronously update with the corresponding status within 10 seconds of submission. Only the first 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. | Test ID Pattern | Resulting Status | | - | - | | 989\*\*\* | `noyo_review` | | 767\*\*\* | `waiting_on_carrier` | | 545\*\*\* | `action_required` | | 323\*\*\* | `unable_to_connect` | | 212\*\*\* | `move_to_carrier_authorization` | ## Carrier configurations [Dynamic config](/docs/groups/mapping/explicit-vs-dynamic-configuration#dynamic-config-automap) 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](/api-reference/groups/configurations/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.* Northeast Delta Dental groups will be configured with a `master_agreement_number` string, which is the primary group identifier, along with a list of one or more `groups` (9-digit numeric code) to categorize employees enrolling in coverage. ```json theme={"system"} { "group_id": "da8d32cc-ce9d-4cf3-9360-733ee0023f1f", "carrier_id": "6ecb26f1-da0f-40b3-9e9a-3272aa17d70e", "configuration": { "master_agreement_number": "123456789", "groups": [ { "group_identifier": "23456789", "group_name": "AcmeCo group 1" } ], "subgroups": [ { "subgroup_identifier": "00001000", "subgroup_name": "AcmeCo subgroup 1" } ], "divisions": [ { "division_identifier": "0001", "division_name": "AcmeCo division 1" } ] } } ``` ### Get the plan configuration from Noyo *The details in [the plan configuration](/api-reference/groups/plans/get-group-plan-list) should be used to [map each Noyo plan to the corresponding plan in your own system](/docs/groups/mapping/mapping-plans-and-account-structures). 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.* Some Northeast Delta Dental plans are only available for employees in certain groups. Northeast Delta Dental plans will include a `plan_configuration` \*\*\*\*block with `group_identifiers` , `subgroup_identifiers`, and `division_identifiers` fields containing lists of string identifiers. The identifiers will match the groups, subgroups, and divisions in the carrier configuration respectively, and describe which groups, subgroups, and divisions are eligible to enroll in the plan. For Northeast Delta Dental, the 9-digit `group_identifier` for dental coverage will often match the `master_agreement_number`. Vision coverage may have a unique 9 digit `group_identifier`. ### 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. Member snapshots missing a `carrier_config` section or with incorrect config data will result in a 422 error.* Snapshots with Northeast Delta Dental coverage may include an optional `group_identifier` , `subgroup_identifier` , and `division_identifier` that matches the corresponding values in the group carrier configuration. For Northeast Delta Dental, there may often be only one of each respective identifier allowed for a plan. If the caller omits any values, Noyo will attempt to resolve the correct identifier in cases where only one option is available for the member's enrollment. ```json theme={"system"} { "group_identifier": "23456789", "subgroup_identifier": "00001000", "division_identifier": "0001" } ``` ## Carrier-specific requirements ### Validations Noyo will validate the following based on the member carrier configuration: * The group, subgroup, and division specified is valid for the group * The provided group, subgroup, and division identifiers are valid for the plans specified in the relevant coverages * Requests to add or modify coverage contain plans that are available to the group, subgroup, and division fields specified This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.