If you are looking to upgrade from Pro Web, Address Validation SOAP or Global intuitive 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 Pro Web or Address Validation SOAP (Formerly known as Pro On Demand) to Experian Address Validation you will need to understand the differences in integration approach and how to prepare for this.

Considerations

  • User Experience (UX) - requires a change in workflow; changes to the user input form are required.
  • Experian Address Validation can be much more interactive compared with previous versions of Address Validation SOAP, therefore more requests may be made, using the Autocomplete search method.
  • Implementation change - going from SOAP to RESTful web services.
  • Experian Address Validation forgoes the traditional address layout functionality in favor of returning a global 7 line address collection along with a full component breakdown. The 7 lines are for displaying back to the end user whilst the full component collection allows for specific components to be entered into relevant database fields.
  • Pro Web customers should understand the additional security considerations of calling out to an external web service - opening ports/firewalls etc.

Security

Experian have recently updated to token authentication instead of username/password credentials. Customers will not be able to use existing username/passwords from previous versions of Address Validate SOAP when using Experian Address Validation.

A token can be passed through as a Request Header:

Auth-Token = a1b234c5-a1bc-1234-a1bc-123a4567891bc

If you have the Global Intuitive and are upgrading to the Experian Address Validation, please review the requirements below:

  • Change GET to POST on /search
  • The search term now needs to go in the body of the /search request (see API specification for an example)
  • Change the header parameter from a URL argument to an auth-token in /search
  • Change the /search endpoint response in parsing from GET to POST
  • Change the header parameter from a URL argument to an auth-token in /format