BigDataCloud Reverse Geocoding
Free reverse geocoding with no API key — coordinates to locality, city, country, and administrative divisions. The free tier is the client-side endpoint, intended for browser use; it requires an Accept header and is rate limited per IP.
🟢 Online · 201 ms
92.24%
Unlimited (client-side), no key for basic endpoints
No key required
Is BigDataCloud Reverse Geocoding down right now?
No — BigDataCloud Reverse Geocoding was up at our last check (Fri, 06 Nov 2026 08:20 UTC): HTTP 200 in 201 ms. It answered 92.24% of our hourly checks over the last 30 days.
We check every tracked API hourly from Cloudflare's network; this page is rebuilt every few hours. For the value right now, query the public JSON API or the MCP server.
Free alternatives (live ranking)
- ipapi.co — 🟢 Online · 1,000 calls/day, no key required
- 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)
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 down right now?
At our last check (Fri, 06 Nov 2026 08:20 UTC) BigDataCloud Reverse Geocoding was up, with HTTP 200 in 201 ms. We check it every hour, and it answered 92.24% of checks over the last 30 days.
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://api.freeapi.watch/badge/bigdatacloud-reverse.svg" alt="BigDataCloud Reverse Geocoding Status"/></a>