Description
Returns distance between user-provided geocode for a property with that from Verisk. Distance could fall in three categories:
- 0-35 meters
- 35.1-100 meters
- Over 100 meters
Technical Details
- REST URL’s
- User Acceptance Environment (UAT)
- https://gatewayuat.verisk.com/underwriting/buildingstructure/geocode/accuracycheck/v1
- Production (PROD)
- https://gateway.verisk.com/underwriting/buildingstructure/geocode/accuracycheck/v1
- 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
- SearchType :- S(strict only)
- Street1 :- Request.Body.Address.Street1
- Either City and StateCode or Zip is required
- City :- Request.Body.Address.City
- StateCode :- Request.Body.Address.StateCode
- Zip :- Request.Body.Address.Zip
- Logitude :- Request.Body.Location.Longitude
- Latitude :- Request.Body. Location.Latitude
- 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