Policy Numbers Now in Quote Responses
The Quote response object now has two (nullable) policy numbers in its response: boundPolicyNumber and originatingPolicyNumber.
The Quote response object now has two (nullable) policy numbers in its response: boundPolicyNumber and originatingPolicyNumber.
Similar to other states like OH and FL, we will now prevent finalizing a quote until a decision is made for every driver in the following states:
There is now a way to register that a quote has been shown to a user. Providing Root a signal that a quote was viewed by a customer will help ensure a more customized coverage offering, allowing us to segment conversion by which quote a customer is shown initially. Root may then tweak the default suggested coverages based on this signal in order to improve conversion.
We now support a new quoting option: options.telematics.
We have added the following webhook events:
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.
We have a new feature in the suggested coverages endpoint to return the monthly and full term payments for each coverage package when the quote's status is quoted.
We've added human-readable descriptions to coverage attributes in the Available Coverages endpoint. This makes it easier to display helpful context to users when rendering a coverage selection UI.
We’ve improved validation error messages to highlight the specific field that caused the error. This makes it easier for your integration to identify issues and handle them more precisely.
We’ve added support for exposing per-coverage pricing directly in quote responses. This applies to most coverages and enables your integration to present the cost of individual coverage selections.