International Address Validation: One API, Many Address Formats
Linda Koeleman, Customer Success Lead

International Address Validation: One API, Many Address Formats
An address form is usually built for the country the business started in. It works until the first order arrives from somewhere else, and then it produces a stream of failures that look like customer error but are not: the form is rejecting perfectly valid addresses because they do not look like the ones it was designed for.
International address validation, which many vendors sell as international address verification, is the practice of checking addresses against the rules and data of the country they are actually in, rather than the country your form was written for.
Why international addresses break validation
Four assumptions cause most of the damage, and every one of them is false somewhere:
- "The postcode is numeric." UK postcodes are alphanumeric (
SW1A 1AA), Canadian and Dutch ones are mixed, and Ireland's Eircodes are alphanumeric and identify individual properties. - "Every address has a postcode." Ireland had no general postcode system until 2015, and several countries still have none.
- "The house number comes before the street." It does in the UK, the Netherlands and the US. It comes after in France, Germany, Spain and much of Europe.
- "There is one line for the town." Many countries need a district, a province, a state or a region as well, and treat it as mandatory.
A regular expression written against one country's format will reject valid addresses from most others. This is the single most common cause of "we cannot ship to your country" messages that the business never intended to send.
Address formats that do not look like UK addresses
A few concrete differences worth designing for:
- Germany and France: street number after the street name; the postcode precedes the town on the same line.
- The Netherlands: postcode is four digits plus two letters, and the combination of postcode and house number identifies an address exactly, which is why Dutch forms ask for those two fields and nothing else.
- Ireland: the Eircode is a seven-character code identifying an individual delivery point, not an area.
- Spain: floor and door designations (
3º izq) are a normal part of the address, not an afterthought. - Belgium and Luxembourg: bilingual place names, so the same town legitimately has two spellings.
The practical consequence is that a single fixed set of form fields cannot serve every country well. The better pattern is to let the country selection change the fields, their order and their labels.
What international coverage actually means
Vendors advertise "240+ countries", and that number hides three very different levels of service:
- Verified: the address is checked against that country's authoritative address file. This is what you actually want, and it exists for a minority of countries.
- Parsed and formatted: the address is split into components and rendered in the local convention, but nobody confirmed it exists.
- Format-checked: the postcode matches the country's pattern. That is all.
All three get counted in a coverage number. Ask which level applies to the countries that matter to you, and be suspicious of a list that does not distinguish them. Two providers can both claim global coverage while offering completely different guarantees for the same country.
Validating at the border of your data
A workable approach for a business selling across several countries:
- Ask for the country first, before anything else, and adapt the form to it.
- Use verified validation for your core markets, where the volume justifies the data cost and the failure cost is real.
- Use parse-and-format for the long tail, so an order from a country you serve twice a year is stored cleanly rather than rejected.
- Never hard-block on a validation failure for an international address. Warn, suggest, and let the customer confirm. The rate of legitimate addresses that fail is much higher across borders than within one country.
- Store the country code separately and in ISO form. Half the international address problems in any database are actually country identification problems.
Where Pro6PP fits
Pro6PP is a cross-border address API. Address validation, autocomplete and lookup are available for England, the Netherlands, Belgium, Germany, France, Italy, Luxembourg, Denmark, Austria, Switzerland and Spain, with reverse geocoding available globally.
That set is deliberately deep rather than wide. Every country in it is checked against address-level data, not just format-checked, and every one returns the same structured response, so an English order and a German order arrive in your database in the same shape. Where a country publishes a national address register, that is our source: the BAG in the Netherlands, the BAN in France, DAR in Denmark, and the official registers in Austria, Switzerland, Luxembourg and Italy. Where it does not, as in England and much of Germany, we build on OpenStreetMap combined with official postcode and regional data, and say so. If you sell across Europe from a UK base, that is the awkward part of the problem solved. The domestic half of the same problem is covered in our guide to UK address and postcode APIs, and if the terminology is new, start with what validation and verification actually mean.
Frequently asked questions
What is international address validation?
Checking an address against the addressing rules and, where available, the authoritative address data of the country it belongs to, rather than applying one country's format rules to every address.
Why do international addresses fail my address form?
Usually because the form assumes a numeric postcode, a fixed field order, or that a postcode exists at all. Those assumptions are false in many countries, so valid addresses are rejected as invalid.
Does any provider verify addresses in every country?
No. Providers cover a large number of countries at some level, but genuine verification against an authoritative file exists for a minority of them. The rest are parsed, formatted or format-checked. Ask for the level per country.
Should I block a customer whose international address fails validation?
No. Warn and offer a suggestion, then let them confirm. Legitimate addresses fail international validation often enough that hard-blocking will cost you real orders.
How should I store international addresses?
Keep the country as an ISO 3166-1 alpha-2 code in its own column, keep the address components in separate fields rather than one free-text blob, and keep a formatted version for printing labels. That combination survives a change of provider.
