While creating, updating, or getting a quote, the alternatives for each coverage selection, along with the expected price delta for choosing that alternative, can optionally be included in the response by using the query parameter:?include_coverage_selection_alternatives=true.
In the following states, we will begin requiring a selection for Roadside Assistance (roadside) coverage for each vehicle:
We will soon begin preventing quote finalization until a decision has been made for every driver in Connecticut (CT) and West Virginia (WV). This change will be implemented in the coming months.
The following seven markets will all be receiving Rideshare coverage (sometimes called Transportation Network Coverage) in the coming months:
The Quote response object now has a fifth key in the "value object" returned, inferredValue. When this property has a value, it means that the API has inferred a value different than the one submitted (or in the place of an omitted value) in order to estimate the price of the quote, because the submitted value is invalid for computing a price in some way.
This update covers two updates that will be released in MT simultaneously. The two changes are Roadside Assistance Coverage and Required Driver Decisions
We’ve added a new Auth endpoint to refresh an existing agency-scoped bearer token without requiring you to rediscover your token lookup parameters.
This update covers two updates that will be released in DE simultaneously. The two changes are Roadside Assistance Coverage and Required Driver Decisions
We have a new attribute in the Get suggested coverages response that represents the priority ranking for each coverage package recommendation.
The Quote response object now has two (nullable) policy numbers in its response: boundPolicyNumber and originatingPolicyNumber.
