In order to access address searching and verification functionality, the request has to be authenticated.
There are two ways to make an authenticated API request:
The **Auth-Token **HTTP request header has to be passed with the GET request. For example:
GET https://api.experianmarketingservices.com/capture/v1/search-address/text?query=Clapham%20Court%2C%20Kings%20Avenue%2C%20LONDON&country=GBR HTTP/1.1
**Auth-Token: 55929877-683b-856c-d3b8-7047fcf0582a**
Ensure your token works before proceeding. For example, using cURL:
curl -XGET -k --header "Auth-Token: 55929877-683b-856c-d3b8-7047fcf0582a"
"https://api.experianmarketingservices.com/capture/v1/search-address/text/?query=Clapham%20Court%2C%20Kings%20Avenue%2C%20LONDON&country=GBR"
Alternatively, the token (auth-token) can be passed as a query parameter in the URL endpoint. For example:
GET https://api.experianmarketingservices.com/capture/v1/search-address/text?query=Clapham%20Court%2C%20Kings%20Avenue%2C%20LONDON&auth-token=<your auth-token value>&country=GBR HTTP/1.1
Permitted URLs
Address Validate API REST supports Cross Origin Resource Sharing (CORS). This is a specification developed by W3C that allows browsers to make cross-domain requests thus enabling client side integrations. When making a request, the browser will add an origin request header. The API will then respond with a CORS specific response header denoting the origin domains allowed to make requests to the API.
CORS Supported OS and Browsers: