Overview

We've changed our available coverages in GA to now require an enhanced modifier with the value "Y" or "N" to be sent when UM/UIM coverage is selected. Previously, this enhanced modifier was not required.

This breaking change went into effect on December 18, 2025 and was announced in this related changelog post.

To prevent this breaking change from affecting your integration, Root will temporarily maintain the legacy API behavior for requests and responses until your integration has been updated to handle the new behavior. If the enhanced modifier is not included in the UM/UIM coverage attributes for a GA quote, the legacy behavior defaults the enhanced modifier to "Y".

Note: The enhanced modifier is not required if UM/UIM coverage is declined.

The Get Suggested Coverages endpoint now adds the enhanced modifier when UM/UIM coverage is selected for GA quotes. During quote creation or updates, whenever UM/UIM coverage is selected in GA, the enhanced modifier must be included in the coverage attributes per vehicle.

Does Your Integration Need Updating?

Depending on how you have integrated with Root's API, there may be no additional work on your part. If you are utilizing one of the options returned by the Get Suggested Coverages endpoint and not making further coverage customization, then no integration changes should be needed on your part (since the suggested coverages will always be returned in a format the create/update endpoints will accept). You may also use the Get Available Coverages endpoint to verify that all coverages are represented properly and that you are including all expected attributes.

How to Update Your Integration

Please reach out to your account manager at any point during the process outlined below if you have any questions or concerns.

✅ Strongly Recommended: Dynamically Integrate with Coverages

Root's available coverages per state may change in the future as regulations and rating plans change; therefore, our recommended approach is to dynamically set coverages based on the available coverage options.

See this guide for a quick way to get started with this approach. By integrating dynamically, no code updates would be necessary when coverage changes are made in the future.

⛔ Short-term Solution

If you are statically mapping Root's available coverages, you may update your static mapping to address this breaking change. However, please note that this approach is only a short-term solution, since you will need to update static mappings any time a coverage change is made in the future.

1. Update your integration to include the newly required enhanced modifier when UM/UIM is selected for GA quotes

Related API endpoints:

Valid UM/UIM coverage attributes before the breaking change launched

{
  "symbol": "umuim",
  "attributes": [
    {
      "kind": "limits",
      "name": "Limits",
      "description": "This coverage has limits on the amounts that might be paid out in case of a claim",
      "selection": {
        "description": "$300,000.00 per accident / $100,000.00 per person",
        "perDay": null,
        "perOccurrence": 300000,
        "perPerson": 100000
      }
    }
  ]
}

Valid UM/UIM coverage attributes after the breaking change launched

{
  "symbol": "umuim",
  "attributes": [
    {
      "kind": "limits",
      "name": "Limits",
      "description": "This coverage has limits on the amounts that might be paid out in case of a claim",
      "selection": {
        "description": "$300,000.00 per accident / $100,000.00 per person",
        "perDay": null,
        "perOccurrence": 300000,
        "perPerson": 100000
      }
    },
    {
      "kind": "enhanced_modifier",
      "name": "Enhanced Modifier",
      "selection": {
        "description": "Underinsured/uninsured motorist enhanced", // or "not enhanced"
        "id": "Y" // or "N"
      }
    }
  ]
}

Note: The enhanced modifier is not required if UM/UIM coverage is declined.

2. Notify your account manager when you are ready for Root to upgrade your integration in our test environment

When you are ready to begin testing, your account manager can disable the compatibility bypass in Root's test environment. Your test integration will then begin requiring the enhanced modifier for UM/UIM coverage for GA quotes. Note that your integration will use the new API behavior immediately once Root updates your configuration.

Your account manager can also re-enable the compatibility bypass should testing reveal further integration changes are needed.

To mitigate risk, we highly recommend monitoring and thoroughly testing your integration against our test environment for some time before continuing to the next step. If you run into any issues while validating the upgrade, please notify your account manager immediately, and we can re-enable the compatibility bypass to restore the legacy API behavior.

3. Notify your account manager when you are ready for Root to upgrade your integration in our production environment

After your team is confident that your integration is able to handle the new enhanced modifier for UM/UIM coverage for GA quotes in Root's test environment, let your account manager know when you are ready for Root to disable the compatibility bypass in our production environment. As with our test environment, Root just needs to update your integration's configuration on our side, which will go into effect immediately when we do so.

Again, if you run into any issues while validating the upgrade, please notify your account manager immediately, and we can re-enable the compatibility bypass to restore the legacy API behavior.