VRR License Plate Search


Description

Vehicle Registration Reports give carriers complete and accurate information about the vehicles your policyholders drive. Data elements for License Plate search include vehicle information and is sourced from state vehicle and registration sources.

DPPA restricted states: CA, HI, IA, NH, NV, NY, OK, PA, and VA
Search type unavailable in these states.

Technical Details

  • REST URL’s
    • User Acceptance Environment (UAT)
      • https://gatewayuat.verisk.com/underwriting/vehicleregistrationreport/platesearch/v2
    • Production (PROD)
      • https://gateway.verisk.com/underwriting/vehicleregistrationreport/platesearch/v2

  • 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
    • License Plate :- Request.Body.VehicleLicensePlate
    • License Plate State :- Request.Body.VehiclePlateState


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


Release Notes

  • V1 to V2
    • REST URL updated from /v1 to /v2
    • Plate type response expanded for additional fields. Response now standardized across all request types.
    • Additional fields
      • CorrectedVIN
      • SourceVIN
      • VehicleType
      • VehicleTypeDesc
      • MakeDesc
      • BrandedState3
      • BrandedDate3
      • BrandedCode3
      • BrandedDesc3
      • NameCode1
      • NameCodeDesc1
    • Retired fields
      • ActivityDate
      • NameSuffix1
      • NameSuffix2
      • NameSuffix3