You can think of a token as a key that opens your license. It is a unique, secure alphanumeric code that allows you to use the products covered by your license. You inject it into your integration to call the products that you are licensed for.
The secure token code is only known to you. Experian Data Quality can see your token details but not the secure part of the token that is needed in your integration. If you misplace your secure token code you can retrieve it from the Self Service Portal, under Licenses.
To prevent unauthorised use of your token, it is strongly recommended that you specify the permitted URLs to be used by your browser-based integration.
When a license is activated a token is automatically generated and made available in the Self Service Portal.
You can create several tokens for each license in order to monitor different integrations, websites, web forms or Experian Data Quality products. Alternatively, you can use a single token for all activity.
Your tokens work for all products within the license. If the product that you require a token for is under a different license, you must create a new token for the correct license. If required, you can also disable the old token.
For the per-click products, you can set up alerts to notify you when your credit balance is low. Email notifications will be sent to you based on the limit you specify:
You can create usage reports for all of your accounts, licenses, and products (currently excludes Clean Application & Clean API).
Usage information includes credits used, the number of searches submitted and results returned.
DPV is used by the United States Postal Service to validate whether an address is deliverable. It also provides information on the exact delivery point, for example, an apartment or suite number.
You have encountered a seed address. A seed address is a non-existent address that will deactivate DPV functionality if it is searched upon. Seed addresses are used to prevent the illegal creation of verified address lists.