What we shipped this month: geocoding, IP, time zone and more
A roundup of recent work across the API: new compatibility hosts, faster time zone and elevation lookups, dashboard features, and clearer quota visibility.
Postal code coverage extended to more countries
A postal code lookup is only as useful as the map of countries it actually understands. We have extended the coverage behind /v1/postcode to include more countries than it did before, widening what the endpoint can answer for teams operating outside a single home market.
My Geocode is priced and built for worldwide use, in EUR only, and postal code coverage growing over time is part of what that promise means in practice. The request shape and response fields for /v1/postcode are unchanged, documented in full at /docs/postal-code-lookup/, so nothing about an existing integration needs to change to benefit from the wider coverage now available underneath it.
This matters most for applications that were built with one country in mind and later found themselves serving customers elsewhere. Address forms, shipping calculators, and location-based signup flows all tend to hit a wall the moment a user outside the original target market shows up. Wider postal code coverage means fewer of those moments, without needing to bolt on a second, country-specific data source just to fill a gap.
Coverage growth of this kind is naturally an ongoing effort rather than a single finished task. Postal systems vary a great deal between countries, some highly structured and consistent, others far less so, and closing that gap country by country takes real, continuing work. We plan to keep extending coverage over time, and updates like this one will keep landing as that work continues.
Pricing and quota behavior around the postal code endpoint are unaffected by this expansion. It still counts as a standard request within the free allowance, prepaid credit, or Unlimited package, exactly like every other endpoint on the platform, and a batch of postal codes still counts each one individually rather than the call as a whole.
If your application serves users outside the region it was originally built for, this is a good moment to check whether a country you previously had to handle separately, or skip entirely, is now covered. Full details on the endpoint, including its request parameters, are documented at /docs/postal-code-lookup/, and general pricing across all endpoints is at /pricing/.