If you are looking to upgrade from Pro Web, Address Validate SOAP, Global Intuitive, or a combination of these to Experian Address Validation, you will need to understand the differences in integration approach and how to prepare for this.
If you are looking to upgrade from an on premises installation of Pro Web or our hosted Address Validate SOAP service to Experian Address Validation you will need to understand the differences in integration approach and how to prepare for this.
Supports Autocomplete search type for 245 countries and territories.
Along with custom address formatting, Experian Address validation offers a global 7 line address collection, a full component breakdown, and available metadata for the selected address. The 7 lines are for displaying back to the end user in a consistent manner for all countries and territories across the world, while the component collection allows for specific components to be entered into your database.
Enrich your data with global geolocation as well as business and consumer demographic data with Experian Enrichment.
Experian Address Validation can be much more interactive compared with Address Validate SOAP, therefore more requests may be made, when using the Autocomplete search type.
You might need additional licenses and new authentication tokens to take advantage of all available datasets.
You need to re-integrate your solution against our REST API. Use the below mapping of the requests and have a look at our sample code to get started.
| Address Validate SOAP and Pro Web request | Experian Address Validation request |
|---|---|
| DoSearch using Singleline | /address/search/v1 |
| DoSearch using Typedown | /address/search/v1 |
| DoSearch using Verification | /address/validate/v1 |
| DoSearch using Keyfinder | /address/lookup/v1 |
| DoRefine | /address/suggestions/stepIn /address/suggestions/refine |
| DoGetAddress | /address/format/v1 |
Experian Address Valdation uses token based authentication. Customers will not be able to use existing username/password credentials from Address Validate SOAP when using Experian Address Validation. Existing Auth-Tokens are compatiable when used against the same datasets.
Pro Web customers should understand that Experian Address Validation is a multi-tenant API service and uses rate limiting to ensure our service is available for all our customers at all times. Additionally, you should consider the additional security implications of calling out to an external API, for example firewalls changes.
By updating to Experian Address Validation you can take advantage of additional search types that are optimized for different use cases, from supplying a few search terms to full address validation.
You might need additional licenses and new authentication tokens to take advantage of all available datasets.
While Global Intuitive only supports a fixed response layout, you can define and use your own custom layout with Experian Address Validaton.
To protect your authentication token from being used fraudulently, Experian Address Validation accepts the auth-token in the request header only. Update your integration to send the auth-token in the header instead of a plain text query parameter.
All query parameters of the /search request, for example the search term, have been moved to the request body. You'll find multiple examples in the API specification.
With moving the query parameters to the request body, the HTTP method for the /search endpoint needs to be updated from GET to POST.
You will need to update the parsing of the /format response as new objects have been created for related elements within the components collection. You can find examples in the API specification as well as additional information in the Format response.
