In GA, we now require an enhanced modifier to be sent when UM/UIM (Uninsured/Underinsured Motorist) coverage is selected. This breaking change went into effect on December 18, 2025.

See this guide for how to integrate these changes.

Affected Endpoints

Related API endpoints:

Timeline

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.

Production behavior will remain compatible and non-breaking until you've confirmed with your account manager that your integration is compatible with this change. Similarly, our test environment will remain compatible until you are ready to begin testing against this breaking change.

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. Your account manager can also re-enable the compatibility bypass should testing reveal further integration changes are needed.

Why

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

What Changed

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.

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. Some examples can be found below:

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.

Future-proofing

Root's available coverages per state may change in the future as regulations and rating plans change.

In order to best support evolving coverage options, you may dynamically adjust choices using the representation returned by Root's Get Available Coverages endpoint; see this related guide for more details. If coverage customization is not a requirement for your use-case, you may also simply use our Get Suggested Coverages endpoint.