Authentication

An authorisation token must be passed to Clean Web Service in the HTTP header. A secure token will be provided to you when you purchase a license to use Clean Web Service. This token will grant you access to the functionality and data you are licensed to use.

All requests sent to Clean Web Service must include an HTTP header containing:

• The content type (including the action parameter shown below).
• Your authorisation token.
  A secure authorisation token will be provided to you when you purchase a license to use Clean Web Service. This token will grant you access to the functionality and data you are licensed to use.
• Other standard parameters, such as Accept-Encoding and Content-Length.

Sample:

POST https://api.experianmarketingservices.com/CleanWS
HTTP/1.1
Accept-Encoding: gzip,deflate
Content-Type: application/soap+xml; charset=UTF-8; action="http://www.qas.com/BulkWebService/2011-04/IBulkWebService/ProcessRecords"
auth-token: 001a100-a10a-a101a-101a-1010a1010a10
Content-Length: 2194
Host: api.experianmarketingservices.com
Connection: Keep-Alive
User-Agent: Apache-HttpClient/4.1.1 (java 1.5)