Skip to content
Free API Today

BigDataCloud Reverse Geocoding API

City, region and country for a coordinate, meant for client-side use.
Status
Working
API key
Not needed
Browser calls
Runs in the browser
Latency
445 ms
Docs
www.bigdatacloud.com ↗

Build snapshot, not live. One verifier run on , from the machine that built this site. How we check

Example request

GEThttps://api.bigdatacloud.net/data/reverse-geocode-client?latitude=37.42&longitude=-122.08&localityLanguage=en

Sent from your browser straight to api.bigdatacloud.net. No proxy: this site never sees the request or the answer.

Copy the request

Shell
curl -s 'https://api.bigdatacloud.net/data/reverse-geocode-client?latitude=37.42&longitude=-122.08&localityLanguage=en'

Response stored by the verifier

This is what api.bigdatacloud.net answered when the verifier sent the request above on : HTTP 200, application/json. Arrays are cut to two items and long strings are shortened. It comes from the build snapshot.

application/json · stored
{
  "latitude": 37.42,
  "lookupSource": "coordinates",
  "longitude": -122.08,
  "localityLanguageRequested": "en",
  "continent": "North America",
  "continentCode": "NA",
  "countryName": "United States of America",
  "countryCode": "US",
  "principalSubdivision": "California",
  "principalSubdivisionCode": "US-CA",
  "city": "San Jose",
  "locality": "Mountain View",
  "postcode": "94043",
  "plusCode": "849VCWCC+22"
}

Availability

Up 1 of 1 day checked · 30-day window

What counts as up for this API: an answer within five seconds, a 2xx status, and the JSON body must contain the field "countryName".

Last check: — passed, HTTP 200 in 445 ms.

The check runs from our infrastructure, not from where you are. If you need certainty, send the request yourself above. How the verifier works.

Used in these collections

Questions

Does the BigDataCloud Reverse Geocoding API need an API key?

No. The sample request on this page was answered without a key, token or account.

Can I call the BigDataCloud Reverse Geocoding API from the browser?

Yes. api.bigdatacloud.net answered our verifier with an Access-Control-Allow-Origin header on Oct 3, 2026, so a fetch call from a web page can read the response.

Is the BigDataCloud Reverse Geocoding API working?

At the check on Oct 3, 2026 it returned HTTP 200 with the expected data in 445 ms. The status at the top of this page shows the most recent result we have.

What is the BigDataCloud Reverse Geocoding API good for?

City, region and country for a coordinate, meant for client-side use. It is part of our collection "Free APIs for a weather app": City name for coordinates that came from the device’s geolocation.