HERE Geocoding & Search API
Enterprise-grade geocoding and places search API using HERE's global map data with high accuracy.
🔴 Offline · 291 ms
0%
1,000 calls/month, free key (Freemium plan), no CC
API key
Free alternatives (live ranking)
- 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)
- GeoIP-db — 🟢 Online · Unlimited, no key, no credit card
Compare HERE Geocoding & Search API with…
- HERE Geocoding & Search API vs ip-api.com — 45 calls/min (HTTP only), no key, no credit card
- HERE Geocoding & Search API vs IPinfo — 50,000 calls/month, no key (token extends limits)
- HERE Geocoding & Search API vs GeoIP-db — Unlimited, no key, no credit card
Paid alternatives
- HERE Essential — from $0.50/1000 calls
Frequently Asked Questions
Does HERE Geocoding & Search API require an API key?
Yes, HERE Geocoding & Search API requires a free API key. You can sign up via https://developer.here.com/documentation/geocoding-search-api/dev_guide/index.html.
What is HERE Geocoding & Search API's free tier?
1,000 calls/month, free key (Freemium plan), no CC
Is HERE Geocoding & Search API currently online?
We check HERE Geocoding & Search API 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 HERE Geocoding & Search API
HERE Geocoding is the most generous free tier among commercial-grade geocoding APIs — 250,000 transactions/month with full HTTPS support, autocomplete, and highly accurate reverse geocoding. HERE has decades of automotive map data (BMW, Daimler, and Audi jointly acquired the company in 2015 for their car navigation needs), which shows in unusually good coverage of less-mapped regions like emerging markets and rural areas. Choose HERE when your product needs address autocomplete (as-you-type suggestions), when you want the strongest coverage across diverse geographies, or when you need to scale past what OSM-backed providers offer without immediately jumping to Google Maps-tier pricing.
Common pitfalls
- Free tier is 250,000 transactions/month but a 'transaction' is HERE's term for an API call — geocoding, autocomplete, reverse geocoding all count. Heavy autocomplete usage drains the quota quickly (a search input firing on every keystroke can cost 5-8 transactions per address entry).
- HERE distinguishes between Geocoding, Reverse Geocoding, Discover, Autosuggest, and Lookup endpoints. They look similar but return different shapes — make sure your code matches the endpoint, not just the URL prefix.
- Authentication uses an API key in a query parameter (`apiKey=...`), not a header. The key is therefore visible in server logs and browser history — treat it as semi-public and rotate periodically.
- HERE's free tier terms allow commercial use but require attribution. The specific format is 'Powered by HERE' with a link to their website — check the license terms if you're distributing to end users.
Quick start (bash)
curl "https://geocode.search.hereapi.com/v1/geocode?q=Brandenburg+Gate&apiKey=YOUR_KEY" From our monitoring
HERE has been one of the most reliable geocoders in our monitoring: 99.9% uptime, response times under 300ms globally, and CDN-fronted infrastructure that handles traffic bursts well. The 250k/month free tier reset happens at the start of the calendar month (UTC), and hitting it returns clean 429s with `Retry-After` headers rather than silent failure. The API surface is genuinely well-designed compared to older commercial geocoders — the JSON is clean, the field names are consistent, and pagination works predictably.
Production integration patterns
Debounced autocomplete on address forms
The correct pattern for HERE's Autosuggest endpoint: debounce the input by 200-300ms so you don't fire on every keystroke, only call Autosuggest when input length >= 3 characters, cache results by input string for 60 seconds to avoid re-querying when users backtrack. This turns a naive implementation (5-10 transactions per address entry) into a lean one (1-2 transactions per entry). At 1,000 daily users entering one address each, that's 2,000 transactions/day vs 10,000 — significant on the 250k/month budget.
Server-side proxy pattern (protect the key)
The `apiKey=...` query parameter is exposed in browser network tabs and logs. For production apps, put a thin proxy on your API server that adds the API key server-side. Bonus: rate-limit per-user in the proxy to prevent abuse, log which users hit which endpoints for cost attribution, and swap providers without changing client code. Small overhead, meaningful security.
Compared to the closest paid alternatives
vs Google Maps Geocoding — $200 free credit/month, then $5/1k requests
Google's geocoder is the industry benchmark for accuracy in most first-world markets but starts billing at the first call after your $200/month credit ($5/1k requests). The free credit gives you ~40k requests/month before charges. For personal projects and MVPs, Google wins on accuracy but HERE's 250k/month clean-free tier wins on cost predictability.
vs Mapbox Geocoding — Free: 100k/month · Standard: $0.75/1k over
Mapbox's free tier is 100k requests/month with HTTPS and modern API design. Coverage is competitive with HERE in developed markets, weaker in emerging markets. If you're already using Mapbox for maps, using their geocoder saves an integration; if not, HERE gives you 2.5x the free volume.
Embed this badge
Add a live status badge to your README, docs, or website.
Markdown
[](https://freeapi.watch/here-geocoding) HTML
<a href="https://freeapi.watch/here-geocoding"><img src="https://freeapi-builder.a10ayassine.workers.dev/badge/here-geocoding.svg" alt="HERE Geocoding & Search API Status"/></a>