FREE Client Side Reverse Geocoding to City API

The free client-side Reverse Geocode to City API converts a user's current latitude and longitude into structured locality data — country, state, city, suburb, and postcode — directly from the browser. If coordinates aren't available (for example, the user declines the location permission), the same endpoint can be called without coordinates and will return a best-effort locality via IP geolocation instead. Both flows return the same JSON schema, so your integration doesn't need to handle two different response formats.

This endpoint is client-side only, free to use, and requires no API key. To keep it reliable for everyone, usage must follow our Fair Use Policy: calls must originate directly from the client (browser or mobile app), use the device's current location rather than pre-stored or third-party coordinates, and use the platform's standard location methods (such as the HTML5 Geolocation API on the web). Server-side or batch use cases should use the server-side Reverse Geocoding API instead.

Why is it free? When a user grants location permission, their browser provides accurate GPS coordinates alongside the IP address used for the request. That anonymous pairing helps us continuously validate and improve our IP geolocation accuracy. We don't require an API key and we don't link location data to identifiable individuals. For more detail, see Why is the Reverse Geocoding API free?

Requests that breach the fair use policy — such as server-side calls to the client endpoint — may trigger a temporary IP-level ban, with the endpoint returning HTTP 402. If your application now complies, contact us to review and lift the ban. For a full explanation of the GPS and IP fallback behaviour, read Client-side Reverse Geocoding with IP Fallback.