Experian Address Validation is a real-time address lookup solution that makes it quick and easy to validate, format and enrich addresses from 245 countries and territories. The global REST API can be seamlessly integrated into any form on your website, checkout, ePOS, call centre and a wide range of CRM, ERP and e-commerce applications.
Addresses can also be enriched with additional data in real-time for greater customer insights. Enrichment data includes business information, delivery point and property identifiers, geocodes, consumer demographics, as well as government and health insights.
You can try our different search types using our sample code examples.
Get started with a free 14-day trial of our address validation solution. To request your trial, please fill in the form on the relevant site:
Once you receive your trial API token, you can get up and running in minutes with client-side sample code. If you have any questions during implementation, please contact the Support team in your region.
Transliteration or Unicode is the process of character-set mapping that involves converting characters from one alphabet to another. This improves the user experience when populating a form and the accuracy of address capture by allowing users to input their address in their own native alphabet or character set, while maintaining a common output in a target character set for an organization to process. This functionality is frequently used by organizations with global customer bases, which need a consistent and readable language for customer onboarding, service delivery, customer support, and more.
Experian Address Validation supports over 40 different character sets, including Latin, Greek, Cantonese, Japanese, Korean, Cyrillic, and Russian. You can choose to display the address results in the local character set or latin alphabet for the user to select from.
Address transliteration is available for the following countries: Belarus, Bulgaria, China, Czech Republic, Finland, Greece, Hong Kong, Hungary, Israel, Japan, Kazakhstan, Korea, Latvia, Macao, Moldova, North Macedonia, Poland, Romania, Russia, Slovakia, Taiwan, Ukraine, and Vietnam.
Below are some examples that show the address input in its original character set and the output after it has been transliterated.
Location biasing is when the geographical location of the user entering the address influences the relevance and order of the address results returned. This can be beneficial when your organization expects the address results to be in a specific country or location. The addresses closest in proximity to the user will appear first in the address suggestions list. As addresses local to the user are prioritized, this helps to eliminate confusion in scenarios where the street name is common and may exist in several cities, states or even countries. Reviewing a list of location biased results also reduces the time taken by the user to select the correct address.
The functionality relies upon the user IP or device location, which the user has to provide their permission to be used. Location biased search functionality is available automatically for eligible countries and can be deactivated if not required during API implementation. If no location is given by the user, the results will be alphabetical depending on the country datasets that the organization is licensed for.
Below is an example of the address suggestions with and without location biasing in use. In the example we used the coordinates for Calabash (33.893,-78.568242), a town on the border between North and South Carolina, USA:
|Ordinary suggestions list||Location biasing suggestions list|
Fuzzy matching is the process of intelligently searching for an address, approximately matching the address information provided by the user to addresses in the authoritative reference dataset (i.e. from Royal Mail, USPS, Australia Post), and returning all likely possibilities for the user to select from. This is useful when the user provides too little or too much information, inputs the address in the wrong format or includes a typo.
Experian Address Validation leverages advanced fuzzy matching logic to deliver the most approximate search results for the user to select from, based on a degree of confidence, rather than an exact match. The solution intelligently recognizes and works around the errors below, reformats the address if needed and includes missing elements to deliver a correct, complete, and formatted address.
Abbreviations – users enter abbreviations for certain address components. For example, Av for Avenue, Blvd for Boulevard, Rd for Road as well as Ch for Chemin (French) or Str for Straße (German).
Typos – users make errors in data entry, especially when on mobile devices or spelling addresses phonetically. For example, entering an 'n' instead of an 'm' or entering 'streeet' instead of 'street'.
Incorrect ordering or format – users don’t always enter the address in the way it appears on an envelope. For example, enter the town or city first, followed by the street and building number.
Missing or additional spaces – users add or miss spaces between words or even within words without realizing.
Missing or additional information – users provide too little or too many address elements when searching for an address. For example, leave out the property/building number.
If the address input cannot be matched to any likely address, a "No matches" message will be shown to the user. Below is an example of fuzzy matching in practice, whereby the user has made an error in data entry and the sophisticated algorithms recognize this and return the relevant address.
Our service correctly classifies and rearranges components to find the intended address.
Too little information
Our service correctly determines the building number and the postal code.
Our service provides recommendations for both "North Buck Creek" and "New Buck Creek".