Geoapify

Geocoding, reverse geocoding, and places search API built on OpenStreetMap with routing and isochrone support.

Status
🔴 Offline · 997 ms

30-day uptime
0%

Free tier
3,000 calls/day, free key, no credit card

Auth
API key

Last 30 days

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 Geoapify with…

Geoapify vs Nominatim (OpenStreetMap) — 1 req/sec, must set User-Agent, no key
Geoapify vs ip-api.com — 45 calls/min (HTTP only), no key, no credit card
Geoapify vs IPinfo — 50,000 calls/month, no key (token extends limits)

Paid alternatives

Geoapify Pro — from $19/mo

Official docs ↗

Frequently Asked Questions

Does Geoapify require an API key?

Yes, Geoapify requires a free API key. You can sign up via https://apidocs.geoapify.com/.

What is Geoapify's free tier?

3,000 calls/day, free key, no credit card

Is Geoapify currently online?

We check Geoapify 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 Geoapify

Geoapify bundles geocoding, reverse geocoding, places search, routing, and isochrone maps under one free API key with 3,000 calls/day. It is OpenStreetMap-backed and suits projects that want a single vendor for multiple location features without paying for separate Google Maps services.

Common pitfalls

The `demo` API key shown in documentation URLs returns a 401 for all endpoints. Registration is required to get a real free key — it is free, instant, and requires no credit card.
The 3,000 calls/day quota is shared across all Geoapify products under one key. If your app calls both geocoding and routing APIs, both count against the same budget. Plan your call distribution accordingly.
Geocoding results are returned as GeoJSON FeatureCollections. The top-level `properties` object on each feature contains the address fields, but the structure differs between forward geocoding (`formatted`, `street`, `housenumber`) and reverse geocoding (`address_line1`, `address_line2`). Parse each separately.
The Places API (point-of-interest search) uses a different endpoint path (`/v2/places`) from geocoding (`/v1/geocode`). Confusing the paths returns 404 errors that look like auth failures due to how Geoapify formats error bodies.

Quick start (bash)

curl "https://api.geoapify.com/v1/geocode/search?text=Eiffel+Tower+Paris&lang=en&limit=1&apiKey=YOUR_KEY"

Embed this badge

Add a live status badge to your README, docs, or website.

Markdown

[![Geoapify Status](https://freeapi-builder.a10ayassine.workers.dev/badge/geoapify.svg)](https://freeapi.watch/geoapify)

HTML

<a href="https://freeapi.watch/geoapify"><img src="https://freeapi-builder.a10ayassine.workers.dev/badge/geoapify.svg" alt="Geoapify Status"/></a>