FOR DEVELOPERS / FROM REQUEST TO REFERENCE

A little code.
A world of context.

Bring postcode, address and nearby-location search into the experience you’re building. Try a real request before you write your integration.

01START WITH A REQUEST

Find your
first response.

Choose your lookup, copy the request and inspect the response. For an interactive view of live results, open the playground.

Open the live playground
TERMINAL / CURL
curl --fail --get \
  'https://api.postcoders.co.uk/v1/postcodes/SW1A%201AA' \
  --header 'Accept: application/json'

Find a postcode centroid and its geographic context.

02THE DETAILS THAT MATTER

Build for the
whole response.

01

Check the coordinate type.

Use a postcode centroid for your area context. Check coordinate_accuracy on address results, and handle postcodes with no published coordinates.

02

Handle limits gracefully.

Respect a 429 response and the Retry-After header. Debounce address input and cancel searches your customer has already replaced.

03

Keep an alternative path.

Let your customer enter an address manually when no open record matches. Treat empty results separately from a connection problem.

04

Carry the attribution.

Follow the source licences when you use or redistribute results. Check the coverage page before relying on a location in your product.

There’s a place to start

Your next feature
starts somewhere.

Start with your postcode or part of an address.

Find a place