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 (for example, country, state, city) in the browser. If coordinates aren’t available—such as when the user declines permission—the same endpoint can be called without coordinates to return a best-effort locality via IP geolocation. In both cases you receive the same JSON schema, simplifying integration.

This endpoint is client-side only and free to use with no API key. To ensure reliability for everyone, usage must follow our Fair Use Policy: calls originate directly from the client environment, use the device’s current location (not pre-stored or third-party coordinates), and employ platform-appropriate methods (e.g., the HTML5 Geolocation API on the web). If your use case requires server-side processing or batch inputs, use the Server-side Reverse Geocoding API, which provides equivalent functionality with API-key authentication and a monthly free allocation.

• Endpoint. GET /data/reverse-geocode-client for both “with coordinates” and “no coordinates” flows.
• Consistent fields. Typical properties include countryName, principalSubdivision, city/locality, postcode, and lookupSource (reverseGeocoding or ipGeolocation).
• Language control. Use localityLanguage to return labels in your preferred language.

Why is it free?

There’s no trick. When you call the client-side endpoint with permission, the browser supplies accurate coordinates; we observe the IP address used for that call. This anonymous pairing of “current GPS” and “observed IP” helps us continuously validate and improve our IP geolocation accuracy, including inputs to the Daily IP Geolocation Accuracy Report. We do not require an API key for the free client endpoint and we do not link the location data to identifiable individuals—see Why is the Reverse Geocoding API free? for details.

Policy compliance and misuse handling

Requests that breach the Fair Use Policy (for example, server-side calls to the client endpoint or processing pre-stored coordinates) may trigger a temporary IP-level ban. In such cases, the endpoint returns HTTP 402 with guidance to switch to the Server-side Reverse Geocoding API. If your application now complies, contact support to review and lift the ban.

For a high-level explanation of permission handling and the unified response, see Client-Side Reverse Geocoding with IP Fallback . To explore the broader product family, visit Reverse Geocoding and IP Geolocation.