Verisk Mileage Model Plus Odometer


Description

Verisk Mileage Model Plus Odometer is a solution that uses available odometer data or Verisk’s analytics to generate an annual mileage figure. Our mileage tools help insurers underwrite a policy or prepare for renewal.

Technical Details

  • REST URL’s
    • User Acceptance Environment (UAT)
      • https://gatewayuat.verisk.com/underwriting/mileageconfirm/estimate/v1
    • Production (PROD)
      • https://gateway.verisk.com/underwriting/mileageconfirm/estimate/v1

  • HTTP Method
    • POST

  • Headers (XML)
    • Content-Type: application/xml
    • Accept: application/xml
    • Authorization: Bearer <access token retrieved from Security Token Service>
      • Token received from Security Service should be used as Bearer

  • Headers (JSON)
    • Content-Type: application/json
    • Accept: application/json
    • Authorization: Bearer <access token retrieved from Security Token Service>
      • Token received from Security Service should be used as Bearer

  • Required Parameters
    • OrgId :- Request.Header.Authorization.OrgId
    • ShipId :- Request.Header.Authorization.ShipId
    • Marital Status :- Request.Body.Drivers.Driver.MaritalStatus
    • Gender :- Request.Body.Drivers.Driver.Gender
    • Driver ID :- Request.Body.Drivers.Driver.DriverId
    • DOB :- Request.Body.Drivers.Driver.DOB
    • Year Licensed :- Request.Body.Drivers.Driver.YearLicensed
    • VIN :- Request.Body.Vehicles.Vehicle.VIN
    • Driver ID :- Request.Body.Vehicles.Vehicle.DriverId
    • Vehicle Use :- Request.Body.Vehicles.Vehicle.VehicleUse
    • Year :- Request.Body.Vehicles.Vehicle.Year
    • Is Leased :- Request.Body.Vehicles.Vehicle.IsLeased
    • State :- Request.Body.Policy.StateCode
    • Zip:- Request.Body.Policy.Zip
    • BI Limit Claimant :- Request.Body.Policy.BodilyInjuryLimitClaimant
    • BI Limit Occurence :- Request.Body.Policy.BodilyInjuryLimitOccurrence



You can specify that you would like to receive your response as XML simply by setting a Header of "Accept" to "application/xml"
  • Headers
    • Regardless of which URL you are using, the following headers are required
      • Content-Type: application/json or application/xml
      • Accept: application/json or application/xml
      • Authorization: Bearer db6e8bdf3b8ce796d38f2cd4298d252




Samples and Schemas

  • Please contact PLUWClientServices@verisk.com or your Account Manager for Request/Response Samples and Schemas