Geoapify Geocoding API
"The Geocoding API (Forward Geocoding) converts postal addresses into geographic coordinates (latitude/longitude). It returns well-formed and accurate addresses along with their geographical coordinates." [1]
Geoapify Geocoding API converts addresses to coordinates and back, covering forward geocoding, reverse geocoding, address autocomplete, and asynchronous batch processing of up to 1,000 addresses per request, with global coverage. Pricing starts at $59 per month on a subscription model, and a free tier is available at 3,000 requests per day with attribution required. The REST API uses API key authentication, has a published SLA, and is GDPR compliant, making it a practical fit for logistics, delivery route planning, and location analytics teams in Europe and beyond.
Best for / Avoid if
Best for: Prototypes and side projects - free to start, no sales call
Avoid if: You have strict compliance requirements
Scores
- 30 / 100Agent friendliness
- 100 / 100Pricing transparency
- 75 / 100Setup speed
- 35 / 100Docs quality
- 100 / 100Procurement ease
- 35 / 100Trust readiness
Pricing & procurement
- Pricing model
- Subscription [2]
- Published pricing
- ✓ Yes [3]
- Free tier
- ✓ Yes [4]
- Free tier details
- 3,000 credits/day (recurring, no credit card required); limited commercial use; up to 5 requests/second; requires "Powered by Geoapify" attribution on free plan websites. [5]
- Self-serve signup
- ✓ Yes [6]
- Requires sales call
- ✗ No
- Enterprise plan
- ✓ Yes [7]
| Plan | Item | Per | Amount | Source |
|---|---|---|---|---|
| Free | geocoding requests (1 credit each), 3,000 credits/day recurring | month | $0 | source |
| API 10 | platform subscription, 10,000 credits/day (geocoding = 1 credit/request) | month | $59 | source |
| API 25 | platform subscription, 25,000 credits/day (geocoding = 1 credit/request) | month | $109 | source |
| API 50 | platform subscription, 50,000 credits/day (geocoding = 1 credit/request) | month | $179 | source |
| API 100 | platform subscription, 100,000 credits/day (geocoding = 1 credit/request) | month | $299 | source |
| API 250 | platform subscription, 250,000 credits/day (geocoding = 1 credit/request) | month | $609 | source |
| Custom | platform subscription, unmetered credits/day, dedicated servers (geocoding = 1 credit/request) | month (starting from) | $860 | source |
| All plans | single geocoding request (forward, reverse, or autocomplete) | 1 credit per request | - | source |
| All paid plans | batch geocoding (each address in batch counted at 0.5 coefficient, plus 1 credit job creation + 1 credit result retrieval) | 0.5 credits per address (up to 50% savings vs single requests) | - | source |
Capabilities
- Supported actions
- forward_geocode, reverse_geocode, autocomplete, batch_forward_geocode, batch_reverse_geocode [8]
- Regions
- global [9]
- Languages
- multilingual results via ISO 639-1 lang parameter
- Input types
- free-form address string, structured address components (housenumber, street, postcode, city, state, country), lat/lon coordinates (reverse geocoding), partial address string (autocomplete), place ID [10]
- Output types
- GeoJSON, JSON, XML, CSV (batch only) [11]
- Webhooks
- ✗ No [12]
- Sandbox / test mode
- ✗ No [13]
- SDK languages
- JavaScript/TypeScript [14]
- MCP server
- ✗ No [15]
Trust & compliance
- SOC 2
- – Unknown
- HIPAA
- ✗ No [16]
- GDPR
- ✓ Yes [17]
- ISO 27001
- – Unknown
- PCI DSS
- ✗ No [18]
- Published SLA
- ✓ Yes [19]
- Rate limits
- Free: up to 5 req/s; API 10 ($59/mo): up to 12 req/s; API 25 ($109/mo): up to 15 req/s; API 50 ($179/mo): up to 20 req/s; API 100 ($299/mo): up to 25 req/s; API 250 ($609/mo): up to 30 req/s; Custom: unmetered; higher limits available upon request. [20]
- Known restrictions
- OpenStreetMap attribution must always be provided when displaying results, Free plan requires visible 'Powered by Geoapify' attribution, Users storing results must maintain attributions to original data sources, Distributing API requests among multiple accounts to fit into lower pricing plans is prohibited, Batch geocoding is asynchronous - clients must poll for job completion, Batch geocoding maximum 1,000 addresses per request [21]
Developer surface
Integration
- API style
- rest
- Base URL
- https://api.geoapify.com/v1/geocode/search
- Version
- v1
- Versioning
- url
- Stability
- ga
- Auth methods
- api_key
- Idempotency keys
- ✗ No
- Error format
- vendor-specific
- Rate limit
- 5 / second
Adoption & maturity
- Launched
- 2019-01-01
Other Geocoding APIs
Azure Maps Render (Map Tiles)
"Azure Maps is a collection of geospatial services and SDKs that use fresh mapping data to provide geographic context to web and mobile applications."
Lob Address Verification
"Avoid mail missteps and make failed deliveries a thing of the past."
Azure Maps Route
"Use to get the best route between an origin and destination for automobile, commercial trucks and walking routes."
Loqate Address Verification
"Global address verification that ensures you reach your customers, every time."
Geocodio
"The delightfully boring geocoder"
Route4Me
"Industrial Grade Route Planning And Route Optimization Software" that "automates and integrates mission-critical last mile workflows, empowering route planners, dispatchers, drivers, and managers to take your business to the next level."
References
- ↑Description: geoapify.com
- ↑Pricing model: geoapify.com
- ↑Published pricing: geoapify.com
- ↑Free tier: apidocs.geoapify.com · geoapify.com
- ↑Free tier details: geoapify.com
- ↑Self-serve signup: apidocs.geoapify.com
- ↑Enterprise plan: geoapify.com
- ↑Supported actions: apidocs.geoapify.com · apidocs.geoapify.com
- ↑Regions: geoapify.com
- ↑Input types: apidocs.geoapify.com
- ↑Output types: geoapify.com · apidocs.geoapify.com
- ↑Webhooks: apidocs.geoapify.com
- ↑Sandbox: apidocs.geoapify.com
- ↑SDK languages: geoapify.com
- ↑MCP server: github.com
- ↑HIPAA: geoapify.com · geoapify.com
- ↑GDPR: geoapify.com · geoapify.com
- ↑PCI DSS: geoapify.com · geoapify.com
- ↑Published SLA: geoapify.com · geoapify.com
- ↑Rate limits: geoapify.com
- ↑Known restrictions: geoapify.com · geoapify.com
Change history
- 2026-06-15 Score Docs Quality: 15 → 35
- 2026-06-15 Score Agent Friendliness: 10 → 30
- 2026-06-14 API Reference URL: (none) → https://www.geoapify.com/maps-api/
- 2026-06-14 Robots Allows Agents: (none) → Yes
- 2026-06-14 Has Structured Data: (none) → Yes
- 2026-06-14 Capabilities: {} → {"batch":true,"forward":true,"reverse":true,"autocomplete":true}
- 2026-06-14 Summary Md: (none) → Geoapify Geocoding API converts addresses to coordinates and back, covering for…
- 2026-06-14 Score Docs Quality: 0 → 15
- 2026-06-14 Rendering: (none) → static
- 2026-06-14 Llms Txt Present: (none) → No
- 2026-06-14 Status Page URL: (none) → https://status.geoapify.com
- 2026-06-14 Docs URL: (none) → https://www.geoapify.com/api
- 2026-06-14 Score Pricing Transparency: (none) → 100
- 2026-06-14 Scoring Methodology: (none) → Scores are computed deterministically from this profile's published, sourced fi…
- 2026-06-14 Avoid If: (none) → You have strict compliance requirements
- 2026-06-14 Best For: (none) → Prototypes and side projects - free to start, no sales call
- 2026-06-14 Score Trust Readiness: (none) → 35
- 2026-06-14 Score Procurement Friction: (none) → 100
- 2026-06-14 Score Docs Quality: (none) → 0
- 2026-06-14 Score Agent Friendliness: (none) → 10
- 2026-06-14 Score Setup Speed: (none) → 75
- 2026-06-14 Requires Sales Call: set to No
- 2026-06-14 Enterprise Plan Available: set to Yes
- 2026-06-14 HIPAA: set to No
- 2026-06-14 GDPR: set to Yes
- 2026-06-14 PCI DSS: set to No
- 2026-06-14 SLA Published: set to Yes
- 2026-06-14 SLA URL: set to https://www.geoapify.com/terms-and-conditions/
- 2026-06-14 Data Retention Policy URL: set to https://www.geoapify.com/privacy-policy/
- 2026-06-14 Documented Rate Limits: set to Free: up to 5 req/s; API 10 ($59/mo): up to 12 req/s; API 25 ($109/mo): up to 1…
- 2026-06-14 Rate Limit Requests: set to 5
- 2026-06-14 Rate Limit Window: set to second
- 2026-06-14 Known Restrictions: set to OpenStreetMap attribution must always be provided when displaying results, Free…
- 2026-06-14 Auth Methods: set to api_key
- 2026-06-14 Auth Docs URL: set to https://apidocs.geoapify.com/docs/geocoding/forward-geocoding/
- 2026-06-14 API Style: set to rest
- 2026-06-14 Base URL: set to https://api.geoapify.com/v1/geocode/search
- 2026-06-14 API Version: set to v1
- 2026-06-14 Versioning Scheme: set to url
- 2026-06-14 Stability: set to ga
- 2026-06-14 Quickstart URL: set to https://www.geoapify.com/get-started-with-maps-api/
- 2026-06-14 Idempotency Supported: set to No
- 2026-06-14 Error Format: set to vendor-specific
- 2026-06-14 Requires Verification: set to No
- 2026-06-14 Starting Price Usd: set to 59
- 2026-06-14 Price Basis: set to month
- 2026-06-14 Slug: set to geoapify
- 2026-06-14 Launched At: set to 2019-01-01
- 2026-06-14 Notable Customers: set to (none)
- 2026-06-14 Fields Not Found: set to soc2, iso_27001, supported_languages (specific language list not enumerated), d…
Suggest an edit / leave a review
Leave a review or comment
curl -X POST https://apio.sh/api/feedback/geoapify \
-H 'Content-Type: application/json' \
-d '{"kind":"review","rating":5,"body":"Your experience with this API…"}'Suggest a correction to a field (cite a source)
curl -X POST https://apio.sh/api/suggest/geoapify/FIELD \
-H 'Content-Type: application/json' \
-d '{"value":"corrected value","citations":[{"url":"https://source.example/page","excerpt":"supporting quote"}],"note":"what changed and why"}'