Household Driver Solution
Modified on 2019/11/05 16:32 by Administrator — Categorized as: Uncategorized
Table of Contents
[
Hide/Show
]
Description
Technical Details
Samples and Schemas
Description
¶
Our NEW UDI – Household Driver Solution aids carriers in prefilling driver data with just a name and address by leveraging multiple data sources to provide a picture of the household. Discovered drivers may be returned as a household match, address only indicated, or as known associations with the input PNI. Each individual discovered driver record includes a Driver Assurance score that acts as a confidence guide. With our multiple data source approach, we can help carriers target their interest for driver information only or access an expanded solution providing additional detail including household demographics and residence information.
Technical Details
¶
REST URL’s
Production (PROD)
https://gateway.verisk.com/underwriting/undiscloseddriverinformation/householddriversolution/v1
User Acceptance Environment (UAT)
https://gatewayuat.verisk.com/underwriting/undiscloseddriverinformation/householddriversolution/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
Required Parameters
OrgId :- Request.Header.Authorization.OrgId
ShipId :- Request.Header.Authorization.ShipId
Driver Sequence Number:- Request.Body.Drivers.Driver.Sequence
Primary Driver First Name :- Request.Body.Drivers.Driver.GivenName
Primary Driver Last Name :- Request.Body.Drivers.Driver.Surname
Current Street Name :- Request.Body.Addresses.Address.AddressType[Current].Street1
Current City :- Request.Body.Addresses.Address.AddressType[Current].City
Current State :- Request.Body.Addresses.Address.AddressType[Current].StateCode
Current Zip:- Request.Body.Addresses.Address.AddressType[Current].Zip
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
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