Address requirements vary by country. This reference documents the fields, formats, and rules that affect how addresses are collected and validated in each supported country.
For most integrations, you do not need to implement country-specific logic — the address form endpoint returns the correct fields and validation rules for each country automatically. This reference is useful when you need to understand the rules behind the form, debug validation issues, or build custom address handling.
| Country | Code | Postal code format | administrativeArea required | Street/number order | Detail |
|---|---|---|---|---|---|
| Sweden | SE | 5 digits | No | Street before number | Details |
| United Kingdom | GB | Alphanumeric + space | No | Number before street | Details |
| United States | US | 5 digits (or 5+4) | Yes (state) | Number before street | Details |
| Germany | DE | 5 digits | No | Street before number | Details |
| Norway | NO | 4 digits | No | Street before number | — |
| Denmark | DK | 4 digits | No | Street before number | — |
| Finland | FI | 5 digits | No | Street before number | — |
| Netherlands | NL | 4 digits + 2 letters | No | Street before number | — |
| France | FR | 5 digits | No | Number before street | — |
| Spain | ES | 5 digits | Yes (province) | Street before number | — |
| Italy | IT | 5 digits | Yes (province, 2-letter) | Street before number | — |
| Austria | AT | 4 digits | No | Street before number | — |
| Poland | PL | 2 digits + dash + 3 digits | No | Street before number | — |
| Canada | CA | Letter-digit alternating | Yes (province) | Number before street | — |
| Australia | AU | 4 digits | Yes (state/territory) | Number before street | — |
| Japan | JP | 3 digits + dash + 4 digits | Yes (prefecture) | Street before number | — |
| Brazil | BR | 5 digits + dash + 3 digits | Yes (state) | Street before number | — |
| Ireland | IE | Eircode (7 chars) | Yes (county) | Number before street | — |
Countries without a detail page link follow the general patterns described in their row. Detail pages are added as integrations in those markets grow.
The API automatically sanitizes postal codes on input:
- Digits only (SE, NO, DK, FI, DE, AT): all non-digit characters are stripped
- Digits and spaces (GB): spaces are preserved (they are significant)
- Digits and letters (CA, NL, IE): special characters are stripped, letters are uppercased
- Digits and dashes (US, JP, BR, PL): dashes are preserved
You do not need to sanitize postal codes before sending them to the API.
Most European countries do not require administrativeArea. It is required for:
- North America: US (state), CA (province), MX (state)
- South America: BR (state), AR (province)
- Asia Pacific: AU (state/territory), CN (province), JP (prefecture), MY (state), KR (province), ID (province), TH (province)
- Europe: IT (province), ES (province), IE (county)
The address form endpoint handles this — when administrativeArea is required, it appears in the form layout with required: true.
Most countries place the street name before the number ("Sveavägen 1"), but several place the number first ("10 Downing Street"):
- Number before street: AU, CA, FR, GB, IE, LU, US
- Street before number: SE, DE, NO, DK, FI, NL, AT, PL, ES, IT, and most others
This affects how addressLines[0] is formatted, but the API accepts either order for all countries.
- Working with addresses — the address model and full flow
- Rendering the address form — dynamically render country-correct forms
- Address validation — verify addresses before order creation