getAddress.io-compatible endpoints: values now match getAddress.io's formatting

Stable

Towns, organisation names, sub_building_name and building_number on the getAddress.io-compatible endpoints change to match getAddress.io's own formatting.

Upcoming — takes effect 14 October 2026 (00:00 UTC). Announced 6 October 2026 to every account using these endpoints. Until then, responses are unchanged.

What's changing

Our getAddress.io-compatible endpoints (/find, /get and /autocomplete) will format values the way getAddress.io itself did, so integrations moving from getAddress.io get the formatting they were built for.

FieldBeforeFrom 14 October 2026
Town — town_or_city, the town in formatted_address, in /find address strings and in /autocomplete suggestionsLONDONLondon (Royal Mail's mixed case: Stoke-on-Trent, Newcastle Upon Tyne)
Organisation names, wherever they appearPrime Minister & First Lord Of The TreasuryPrime Minister & First Lord of the Treasury
sub_building_name for an organisation with no flat or unit""the organisation name
building_number when an address has none" " (a space)""

Nothing else changes: the same addresses, in the same order, with the same fields — including the paging fields (page, limit, total, next_page) added on 6 October 2026 — and the same pricing (one lookup per /find or /get request).

Do I need to do anything?

Almost certainly not. Check your integration only if it compares town or organisation names character for character, or treats a building_number of " " as present.

Why

These endpoints exist to make moving from getAddress.io straightforward. getAddress.io returned mixed-case towns and re-cased organisation names; now we do too. We've checked our output field by field against getAddress.io's own response: the remaining differences are county and district (local authority), which come from a different source, and latitude/longitude, which we don't yet provide — see Migrating from getAddress.io.

Questions? Email snapaddress@clearpathlabs.co.uk.