[Breaking] Third-party Telematics Consent Removed
We have removed the profile object attribute which accepts customer consent permitting Root to order and use third-party telematics data:
We have removed the profile object attribute which accepts customer consent permitting Root to order and use third-party telematics data:
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 have added a new attribute to the profile object which accepts customer consent, permitting Root to order and use third-party telematics data:
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.
We now support an optional options object in quote requests. The first supported option is invoice_period, which lets you specify whether the quote should assume monthly or pay-in-full billing — ahead of quote finalization.
When requesting policy information, you can now provide policy number or policy ID as the path parameter, which is now named policy_identifier.
The Authenticate bridge link endpoint will now return agentId within the response body.
We have added support for generating a temporary access token for a particular agency: The "Create token" endpoint.