A complicated address API is a choice, not a requirement. Legacy tools bury Royal Mail PAF data behind bespoke SDKs and opaque auth, but all you really need is one authenticated REST call that returns matching addresses as JSON. AutoPostcode does exactly that against ~31M UK addresses, so most teams integrate in minutes.
Why do address integrations get so complicated?
Complexity is usually accidental — layers of SDKs, versioning and inconsistent payloads that grew over time. None of it is required to return an address.
- Mandatory proprietary SDKs to install and maintain
- Confusing multi-step authentication
- Response shapes that differ per endpoint
- Sparse docs with few real examples
- Hard-to-find rate-limit and error behaviour
What does a simple postcode lookup look like?
One request in, JSON out. Here's a lookup with plain fetch — no SDK, no ceremony:
// Look up addresses for a UK postcode
const res = await fetch(
"https://api.autopostcode.com/v1/lookup?postcode=SW1A1AA",
{ headers: { Authorization: "Bearer YOUR_API_KEY" } }
);
const { addresses } = await res.json();
// addresses: [{ line1, line2, town, postcode, uprn }, ...]Prefer cURL? Same endpoint, same shape:
curl -H "Authorization: Bearer YOUR_API_KEY" \
"https://api.autopostcode.com/v1/lookup?postcode=SW1A1AA"Complicated legacy API vs AutoPostcode
| Factor | Legacy API | AutoPostcode |
|---|---|---|
| Integration | SDK + config | One REST call |
| Response | Varies by endpoint | Consistent JSON |
| Auth | Multi-step | Simple API key |
| Time to first lookup | Hours/days | Minutes |
Where do I start?
Follow the API quickstart to get a key and make your first call, read the postcode lookup API reference, and for front-end autocomplete see the JavaScript autocomplete tutorial.
A modern, UK-first alternative
AutoPostcode is the developer-friendly, affordable alternative to Loqate, Fetchify and Ideal Postcodes — the same Royal Mail PAF data, delivered through an API you can actually enjoy using.
Frequently asked questions
Why are address APIs so complicated to integrate?
Legacy address APIs pile on bespoke SDKs, opaque auth flows, inconsistent response shapes and thin docs. That complexity slows every integration, when all most teams need is a clean REST endpoint that returns PAF addresses as JSON.
What does a simple postcode API look like?
A single authenticated GET request with a postcode returns a JSON array of matching Royal Mail PAF addresses. No SDK required — any language that can make an HTTP request can integrate in minutes.
How fast can I integrate AutoPostcode?
Most teams have a working lookup in minutes: get an API key, call one REST endpoint, and render the results. Copy-paste examples and no-code plugins cover the common platforms.
Do I need a special SDK?
No. AutoPostcode is a standard REST API returning JSON, so you use your language's native HTTP client. There's nothing proprietary to learn or maintain.
Is the data the same as the complicated tools?
Yes. AutoPostcode uses Royal Mail PAF (~31M addresses, ~1.8M postcodes), the same authoritative UK source the legacy vendors use — just with a far simpler integration.
How is authentication handled?
Authentication is a simple API key passed with each request. Keys are easy to rotate, and rate limits and errors are documented clearly so you're never guessing.
Ready to get started?
Add Royal Mail PAF-verified UK address lookup to your site in minutes — start free, no card required.