Short answer
For UK addresses, choose an API built on licensed Royal Mail PAF data, then test its suggestions against your own addresses before you integrate it. If you take addresses outside the UK, you want a provider with multi-country coverage instead.
Postio fits the UK case: type-ahead search, every address at a postcode, UDPRN resolution, UK and BFPO coverage, and pay-as-you-go billing with no subscription.
Who this guide is for
You are choosing an address autocomplete API for a UK website: a checkout, a booking form, a sign-up flow or a CRM screen. These are the criteria that decide it.
Autocomplete, postcode list, stored-address check
Three different jobs get sold as "address lookup".
- Type-ahead autocomplete. The customer types a house number, street or business name and suggestions appear as they go. Bullock's buying guide puts the number of characters typed before useful suggestions appear among the things to test in a trial (Lilach Bullock, "Address Validation APIs (2026): 10 Options by Country", read 17 November 2026).
- Every address at a postcode. They type a full postcode and pick from the delivery points on it. Fewer keystrokes, and it copes with forty flats at one postcode.
- Checking a stored address. You already hold it, from an import or a phone order, and want it corrected to postal rules and confirmed as able to receive mail. Bullock defines validation as checking an address against official postal data, correcting and standardising it (Lilach Bullock, 2026).
Most UK forms want the first two, with the postcode list as the fallback.
Why licensed Royal Mail PAF data matters
PAF is Royal Mail's file of UK postal delivery points. Bullock's guide calls it the UK's official postal address file, with several UK lookup services verifying against it (Lilach Bullock, 2026). So ask which file the suggestions come from, and whether the provider licences it directly from Royal Mail: that is the difference between current delivery points and a stale copy of them.
Postio is built on licensed Royal Mail PAF data, and its address coverage is UK and BFPO. That is deliberate: if you take addresses outside the UK, Postio is not your provider.
How to add autocomplete with Postio
- Sign up for a key. The authentication docs show where it goes: every endpoint is a GET returning JSON, with the key in an
x-api-keyheader. - Pick the route for your stack. A plain HTML form takes the drop-in Address Finder: one script tag, a combobox with keyboard navigation and ARIA attributes. React has a component, and there are npm packages, a CLI, an MCP server and SDKs for Python, Go, PHP, Ruby and .NET. On WordPress, the plugin covers WooCommerce checkout and the main form builders.
- Call search as the customer types, then resolve the one they pick:
GET https://api.postio.co.uk/v1/address/search?q=57+wimpole
GET https://api.postio.co.uk/v1/address/udprn/50905588- Run the tests below before you go live.
How a suggestion is resolved by UDPRN
Search returns suggestions only: a udprn and a one-line label for each. When the customer picks one, /address/udprn/{udprn} returns the full PAF record — address lines, post town, organisation, sub_building_name for a flat or unit, postcode — plus OS coordinates and ONS district and ward. Keep the UDPRN with the saved address and you can resolve that delivery point again later without asking the customer to retype it.
That second call is what makes autocomplete safe: the customer picks from real delivery points, so what you save is an address Royal Mail delivers to. The address docs list every field.
How to test it on your own addresses
Bullock's trial list is a sound one: accuracy on your real addresses including the messy ones, autocomplete speed, coverage of flats, rural addresses and new-build streets, the extras you need, and integration fit (Lilach Bullock, 2026). In practice:
- A flat in a converted house, where the flat number should land in
sub_building_name, not be glued to the street line. - A rural address whose locality matters, to see the dependent locality come back.
- A street finished in the last few months: PAF is postal data, so a very new build can be missing.
- A business address, to see
organisation_namefilled in. - The same postcode typed with a space, without one, and in lower case.
Then print a label from what came back and see whether the address survives the journey.
Coverage, county and what you pay for
Postio covers UK and BFPO addresses only, and returns no county field, on purpose: Royal Mail removed the former postal county from PAF in 2000, and post town plus postcode are the only mandatory parts of a correct UK postal address. District and ward come from ONS administrative geography instead, flagged as non-postal.
Billing is pay as you go, with no subscription and no monthly fee, on one account for addresses, emails and phone numbers. Prices are on pricing. Coordinates are the postcode centroid, so routing and distance sorting need another tool.
Selection checklist
| Check | What to ask |
|---|---|
| Dataset | Which postal file, and does the provider licence it directly from Royal Mail? |
| Coverage | UK only, BFPO, or other countries too? |
| Autocomplete | How many characters before suggestions are useful? Keyboard and screen-reader support? |
| Resolve | Does a suggestion resolve to one identified delivery point you can store? |
| Difficult addresses | Flats, rural and new builds tested on your own list? |
| Integration | Plugin, drop-in or SDK for your stack, or JSON to build against? |
| Billing | Per lookup, or a monthly minimum you pay in a quiet month? |
Next step
Start with the 100 free lookups, run the tests above on your own addresses, then read the address documentation for the parameters and fields. Postio's address page is the short version.