Skip to main content

Self Service Portal

The Self Service Portal allows you to manage your Experian products and services, including licenses, tokens and users for the account. You can also get insights by running reports on usage and set up notifications so the right people are alerted when something needs your attention.

Get started

Access the Self Service Portal at https://manage.experianaperture.io

Don't have a user login? Get in touch with your Account Manager or Technical support.


Looking for help with Validation Suite? Go to the user guide.

User management

You can now manage users for your account in the Self Service Portal.

Permission levels

There are two user permission levels:

Consumer
  • Able to access all portal features, including view licenses, manage tokens, create reports, set up notifications and view users for the account.
Administrator
  • Able to access all portal features, including view licenses, manage tokens, create reports, set up notifications and view users for the account. 
  • Can create, edit or delete users.

Note: If your account doesn't have a user with administrator permissions then get in touch with your Experian Account Manager or contact Support.

How do I know what my permission level is?

On the Self Service Portal, click on your username in the top right corner and select Account settings > Access and permissions tab.

Managing users

Users with administrator permissions can perform the following user management tasks.

Creating a new user

To create a new user:

  1. In the top-right corner of the Self Service Portal, click your username > Account settingsAccess and permissions tab.
  2. Click the Add a user button.
  3. Fill in the user's details and select the permission level.
  4. Click Save.
  5. A confirmation pop-up opens. Note that you can't change the email address once the user has been created.
  6. Review the user details, and when you're happy click Create user.

The new user is added to the account. An email will be sent to the user inviting them to the Self Service Portal. Once they have confirmed their email address and set their password, they'll be able to sign in. 

Editing a user

Note that you can't change your own permission level.

To change a user's permission level:

  1. In the top-right corner of the portal, click your username > Account settingsAccess and permissions tab.
  2. On the row for the user that you want to edit, click Edit.
  3. Make the required edits to the user's name or permission level. Note that you can't change the email address.
  4. Click Save. An email will be sent to the user informing them of changes.

Deleting a user

When you delete a user, anything set up by them, such as tokens or notifications, will remain.

Note that you can't delete your own user profile

To delete a user, follow these steps:

  1. In the top-right corner of the portal, click your username > Account settingsAccess and permissions tab.
  2. On the row for the user that you want to edit, click Delete.
  3. In the confirmation pop-up, click Delete user. An email will be sent to the user informing them that their user profile has been deleted.

User management FAQs

This section provides answers to FAQs about tokens.

I need to edit or delete my profile - what do I do?

You cannot edit or delete your own profile, only another administrator can do this on your behalf. If you're the only administrator on the account, you need to give another user administrator permissions or create a new user with administrator permissions. 

I need to change a user's email address - what do I do?

For security reasons, as the user's email address is also their username, you can't change the email address. If you need to update an email address, first you must delete the user and create a new user profile for them. 

All log activities from the deleted user, such as any tokens or notifications that were created by them, will remain but won't be associated with the newly created user. 

Notifications

The Notifications feature is in Beta, but you can test it for yourself here.

Notifications help you to monitor your products and to ensure that

  • there are no interruptions to your service (license date expiring or zero credits remaining)
  • you're aware of any significant changes in behavior (spikes or drops in requests)

Your account is checked daily, and you'll be alerted when the rules you have set are triggered. This means that as long as your notifications are set up appropriately, you'll only need to log in to your account when there's been an unusual activity, or to diagnose a potential issue.

We recommend that you set the notifications levels so that they're only triggered infrequently. Getting too many notifications means they can easily be ignored - so to prevent this, adjust they settings accordingly. We also recommend checking that the notifications are sent to the right users. 

Automatic notifications

There are some notifications that are automatically generated by the system. You can edit these but they can't be deleted:

Your Experian data quality product license is nearing expiry’

  • This is sent to all account users 60 days before any product license expires.

Your Experian data quality product license has expired’

  • This is sent to all account users 0 days before, in other words once a product license has expired.

‘Your Experian data quality product is running low on credits’

  • This is shown only in accounts with Per Click product licenses.
  • This is sent to all account users once there are fewer than the set amount of credits remaining. The amount is 20% of the credits you purchased with your first product (minimum value set will be 500). 

Your Experian data quality product has run out of credits’

  • This is shown only in accounts with Per Click product licenses.
  • This is sent to all account users once there are 0 purchased credits remaining, in other words once a product license has expired.

"Number of requests" and "Number of requests change" notification types

These two notification types are similar, but have slightly different uses.

Number of requests is useful for tracking a static amount as a threshold level.

Some examples of things you could set up to be alerted of:

The product has stopped being used Select the product and set the rule as "Chargeable requests less than (<) 100".

Any failed requests

Set the rule as "Failed requests greater than (>) 0".

Your development team is using too many credits during testing

Select the token they're using and set the rule as "Total requests > 1000".

Your annual license is making more requests than the agreed fair usage amount

Set the rule as "Chargeable requests > 2,740". This is the fair usage amount per day;  the standard amount of fair usage is 1 million,  the rule is checked daily so divide this by 365. 

Number of requests change is useful for being alerted to extreme changes in behavior versus normal behavior for your account. It still looks at the number of requests yesterday, but rather than comparing to a static number (as above) you specify a percentage change that would mean to you that something significant has changed when compared to the number of requests the: 

  • ‘Previous day’ – if your usage tends to be fairly consistent.
  • ‘Same day last week’ – if your usage fluctuates consistently on specific days, dropping at the weekend for example.
  • ‘Average of past 7 days’ – if your usage fluctuates throughout the week. 
  • 'Average of the past month' – if  your usage fluctuates seasonally, rising significantly over the holiday period for example.

Creating and editing notifications

The name of the notification is used as the email subject line, so we recommend giving it a name that is specific and that makes sense to the recipients. For example, for product license about to expire, "Website integration that validates email addresses expires in a month". 

Each notification can be sent to all account users, or you can select specific users to receive specific notifications. See here for details on how to see all the users in an account and how to add new users.

You can't edit the Notification type once it's been saved, but you can delete or disable a notification and replace it with a new one. 

Notification FAQs

This section provides answers to FAQs about notifications. 

How often are notifications sent out?

Every day after midnight GMT.

Can I set up multiple notifications on the same product, license or token?

Yes. In fact, it's a good idea is to have multiple notifications with increasing levels of urgency, reflected both in the notification name and the number of recipients, as the license end date draws nearer, credit balance diminishes or volume used dramatically changes. 

I didn't receive an email, how can I check if one was sent?

There's two things you can check:

  • On the Notifications page there's a column called "Date last sent". This tells you the last time the rule was triggered and an email was sent out to the selected users.
  • Check your junk email folder. To ensure you receive all future communications, please add noreply.dataquality@experian.com to your email address book.

The license end date of one of my products is within the threshold value I set, why didn't I receive an email?

If the product license end date was already the same or lower than the value you entered when you were in the portal setting the rule then we don't send you an email. This means you won't be alerted to things you already know about.

The credit balance of one of my products is lower than the threshold value I set, why didn't I receive an email?

If the product license credit balance was already the same or less than the value you entered when you were in the portal setting the rule then we don't send you an email. This means you won't be alerted to things you already know about.

Tokens

This section provides answers to FAQs about tokens. 

What is a token?

Think of a token as your username and password. When you sign in to a website you need to use your credentials; similarly, when you want to access any of our APIs, you need to provide your token(s).

A token is a unique alphanumeric code that looks like: ab123ab1-abc1-1234-abcd-ab1a123a1a12.

We recommend you treat your tokens like your passwords: keep them secure and change them often.

What is the purpose of a token?

The purpose of a token is to authenticate the requests you send to our APIs.

Additionally:

  • It contains information about the products you are entitled to use through your license.
  • It records product usage.
  • It can be secured to prevent unauthorized parties from using your licensed products.

Where do I find my tokens?

  1. Sign in to the Self Service Portal.
  2. Go to Licenses.
  3. A list of your licenses is displayed. Note that each license has its own tokens. Identify the license whose tokens you want to find and click the associated View details button.
  4. A new page opens, where you can view the tokens associated with the license.

Now you can perform the following actions:

How do I create a new token?

We suggest you create and use multiple tokens. Check out How many tokens should I use? to find out why.

To create a new token:

  1. Follow the steps under Where do I find my tokens?
  2. Click the Add a token button.
  3. A pop-up opens, where you need to provide a name for the new token. Optionally, you can change its status (the default is Active) and manage its security.
  4. Once you’re done, click the Save button to finish creating the new token.

How do I activate a token?

Activate tokens so they can be used to send requests to our APIs.

To activate a token:

  1. Follow the steps under Where do I find my tokens?
  2. Find the disabled token and click the associated Activate button.

How do I disable a token?

Disable tokens to prevent them from being used in requests to our APIs.

To disable a token:

  1. Follow the steps under Where do I find my tokens?
  2. Find the token you want to disable and click the associated Disable button.
  3. In the pop-up that opens, click the Continue button to confirm disabling the token.

How do I edit a token?

You might want to edit a token to:

  • Rename it, so it has a friendlier, easy to distinguish name (which is useful when creating reports, for example).
  • Secure it. Don't forget, you should treat your token like a password.
  • Activate/disable it, so it can/cannot be used to send requests to our APIs. 

To edit a token:

  1. Follow the steps under Where do I find my tokens?
  2. Find the token you want to edit and click the associated Edit button.
  3. A pop-up opens, where you can edit the token: its name, status, and security settings
  4. Once you are done, click the Save button to finish editing the token.

How do I secure my tokens?

If you don't secure your tokens, there's the risk of unauthorized parties using your licensed products, which you may be charged for.

One of the easiest and most effective ways to secure your tokens is to periodically change them, just like you do with your passwords.

You can take additional steps to secure your tokens:

  • Specify CORS origin domains. By doing this, you make sure that only the API requests made from the domains you’ve specified are allowed.
  • Specify permitted URLs. By doing this, you make sure that only API requests made from the URLs you’ve specified are allowed.
  • Whitelist IPs/IP ranges. By doing this, you make sure that only API requests made from the IPs/IP ranges you’ve specified are allowed.

Follow How do I edit a token? to implement the steps listed above.

How do I find out the value of a token?

You need to find out the values of tokens so you can use them to send requests to our APIs.

To find out the value of a token:

  1. Follow the steps under Where do I find my tokens?
  2. Find the appropriate token and click the associated Get token link.
  3. A pop-up opens, where you can see the value of the token and copy it to the clipboard.

How many tokens should I use?

By default, a license comes with a token, which applies to all the products you are entitled to use through the respective license.

However, we recommend you create and use at least one token per environment (development, testing, staging, production).

Consider using multiple tokens for your production environment. This way, it’s easy to monitor and create reports on product usage and different integrations you might have.

Note: You cannot use a token across multiple licenses.

How do I check if a token is working correctly?

To check if a token is working correctly, you need to test it, by making an API call.

For testing API calls, we recommend Postman, which you can download for free. If you need help using Postman, check out the user documentation

You will know if your token is working correctly based on the status code of the response you get from the API:

Status code Is my token working correctly?
200 The request was successful and your token is working correctly.
400 The request was not successful. You might have forgotten to add the token in the request header.
401 The request was not successful. You might have used an incorrect token. Check the Self Service Portal to make sure you’ve used the right token.
403 The request was not successful. The token is valid, but it might be disabled. You can activate it in the Self Service Portal.

My token isn't working. What should I do?

There are several reasons why a token might not be working:

  • The token is disabled. Follow this guidance to activate it.
  • You have run out of credits for a product. Once you deplete the credits for a product, you are no longer able to use any of the tokens associated with the respective product. Contact your Experian Data Quality account manager to purchase more credits.
  • Your license has expired. Once your license has expired, you are no longer able to use any of the products covered by it. Contact your Experian Data Quality account manager to renew your license.

Usage information and reports

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.

Creating reports

  1. Log in to the Self Service Portal.
  2. On the home page, click Reports.
  3. Specify the report details:
    • select the required account and license
    • choose 'All tokens' to report on all of the tokens for that license or select a specific token
    • pick the report type
    • define the date range
  1. Click the Create report button to generate the report.

What type of reports can I create?

  • Address validation - product usage information (credits used, number of searches submitted and results returned) as well as the summary of all installations and users.
  • Address verification - product usage information (credits used, number of searches submitted and results returned).
  • Data Health Check - usage information (credits used, number of searches submitted and results returned) for address, email, and phone products.
  • Email validation - product usage information (credits used, number of searches submitted and results returned).
  • Phone validation - product usage information (credits used, number of searches submitted and results returned).

Delivery Point Validation (DPV)

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.

Why is my account locked?

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.

How do I unlock my account?

  1. Log in to the Self Service Portal.
  2. Click the Unlock DPV button displayed in the banner on the dashboard.
  3. Answer the two questions relating to the seed address you encountered.
  4. Click Unlock DPV.