BigDataCloud Reverse Geocoding
Free reverse geocoding API converting coordinates to addresses with locality, city, country, and postcode data.
🔴 Offline · 437 ms
9.96%
Unlimited (client-side), no key for basic endpoints
No key required
Free alternatives (live ranking)
- Nominatim (OpenStreetMap) — 🟢 Online · 1 req/sec, must set User-Agent, no key
- ip-api.com — 🟢 Online · 45 calls/min (HTTP only), no key, no credit card
- IPinfo — 🟢 Online · 50,000 calls/month, no key (token extends limits)
Compare BigDataCloud Reverse Geocoding with…
- BigDataCloud Reverse Geocoding vs Nominatim (OpenStreetMap) — 1 req/sec, must set User-Agent, no key
- BigDataCloud Reverse Geocoding vs ip-api.com — 45 calls/min (HTTP only), no key, no credit card
- BigDataCloud Reverse Geocoding vs IPinfo — 50,000 calls/month, no key (token extends limits)
Paid alternatives
- BigDataCloud Premium — from $29/mo
Frequently Asked Questions
Does BigDataCloud Reverse Geocoding require an API key?
No, BigDataCloud Reverse Geocoding is freely accessible without registration or an API key.
What is BigDataCloud Reverse Geocoding's free tier?
Unlimited (client-side), no key for basic endpoints
Is BigDataCloud Reverse Geocoding currently online?
We check BigDataCloud Reverse Geocoding every hour. The current status is shown at the top of this page. You can also see the 30-day uptime history in the chart above.
Implementation notes
When to use BigDataCloud Reverse Geocoding
BigDataCloud's client-side reverse geocoding endpoint is one of the few IP-geolocation APIs that works entirely in the browser without exposing a key — the `reverse-geocode-client` endpoint requires no authentication and allows CORS. Use it for browser-based apps that need to convert coordinates to a readable address without a server round-trip.
Common pitfalls
- The keyless `reverse-geocode-client` endpoint is explicitly for client-side use only. Server-side usage at scale will hit undocumented soft limits. For backend batch geocoding, use the keyed `/reverse-geocode` endpoint which has documented rate limits.
- The response includes both an `address` string and structured fields (`city`, `locality`, `postcode`, `principalSubdivision`). The `locality` field is often more accurate than `city` for suburban areas — do not assume `city` is always populated.
- Resolution depends on latitude/longitude precision. Passing coordinates rounded to 2 decimal places (~1.1km precision) will return a district or neighborhood match; 4+ decimal places (~11m) returns street-level results.
- The API returns HTTP 200 with `localityInfo.administrative` and `localityInfo.informational` arrays that vary in length by country. Indexing these arrays by position (e.g., `[0]` for country, `[1]` for state) is fragile — iterate and check the `adminLevel` field instead.
Quick start (bash)
curl "https://api.bigdatacloud.net/data/reverse-geocode-client?latitude=48.8566&longitude=2.3522&localityLanguage=en"Embed this badge
Add a live status badge to your README, docs, or website.
Markdown
[](https://freeapi.watch/bigdatacloud-reverse)HTML
<a href="https://freeapi.watch/bigdatacloud-reverse"><img src="https://freeapi-builder.a10ayassine.workers.dev/badge/bigdatacloud-reverse.svg" alt="BigDataCloud Reverse Geocoding Status"/></a>