HERE Geocoding & Search API guide (coverage, pricing, rate limits, licensing)
**Last updated:** 2026-01-09 | **Updated by:** Coordable | **Sources:** HERE Developer Terms and Conditions, HERE Location Services Coverage Information, Geocoding APIs Pricing Comparison (Bitoff), Free Geocoding APIs List (Ambee)
Table of contents
HERE Geocoding & Search API is a high-quality geocoding service used across automotive, logistics, and enterprise mapping products. It converts addresses, place names, and POIs (Points of Interest) into geographic coordinates (latitude/longitude) and structured location components, with strong parsing for messy user input and robust POI discovery endpoints.
⭐ Excellent Accuracy 🏙️ Strong POI Coverage 🎁 30k Free/Month 💰 Affordable at scale ❌ Limited Storage
Key features:
- Forward + reverse geocoding (addresses ⇄ coordinates)
- POI search & discovery (places, brands, categories, landmarks)
- Autocomplete / suggestions for search boxes and user-entered queries
- Strong address parsing (abbreviations, incomplete inputs, typos)
- Flexible usage in many mapping stacks (not tied to a single map renderer by default)
Advantages and disadvantages
HERE Geocoding & Search is a top-tier provider for address resolution and POI search — especially in Europe and for enterprise use cases — but it comes with important constraints (notably around storage/caching). Let’s look at the trade-offs:
✅ Advantages
Excellent address accuracy
- Strong structured address matching (street + housenumber)
- High-quality results for both urban and rural areas in many regions
- Useful match metadata for ranking and confidence
Solid POI search and discovery
- Search places by name, category, brand, and proximity
- Autocomplete endpoints suitable for typeahead UIs
- Good coverage for enterprise and navigation use cases
Developer-friendly pricing for prototypes → production
- Generous free tier (30k requests/month on common plans)
- Competitive price per 1,000 requests compared to premium providers
- Predictable cost model with volume tiers
Enterprise-grade ecosystem
- Widely used in automotive and navigation products
- Scales well for high-volume apps
- Long-standing location technology vendor
❌ Disadvantages
Storage / caching restrictions
- Not designed for building your own long-term geocoded address repository on standard terms
- Caching is limited and governed by specific conditions
Rate limits are plan-dependent
- No single “universal” published QPS for every plan and endpoint
- Lower tiers may have strict daily limits and RPS caps
Docs + portal transition in 2026
- HERE has been migrating experiences between portals
- Expect account / documentation URLs to evolve (plan accordingly)
Coverage
HERE Geocoding & Search is designed for broad international use, and HERE publishes service availability information that evolves over time. The interactive map below is an estimation of coverage/accuracy by country computed by Coordable (not an official HERE statement).
Interactive coverage map
● Excellent - Consistently strong address resolution + POI search
● Very Good - Strong in most areas, some regional variation
● Good - Good baseline geocoding, POIs vary
● Standard - Baseline coverage (all other countries)
Important note: this interactive map is a Coordable estimation (not official HERE coverage). For official availability notes and updates, refer to HERE’s coverage information page.
More info:
Address types supported
HERE Geocoding & Search supports both structured and unstructured queries, including:
-
Full housenumber addresses:
425 W Randolph St, Chicago, IL -
Street / locality queries:
Kennedyplein Eindhoven -
Administrative areas:
Andorra,Catalonia,Île-de-France -
Postal codes:
75001,1000,SW1A -
POIs:
Eiffel Tower,Starbucks,Airport,Hospital -
Category queries:
restaurant near 41.387,2.170
Practical strength: HERE is often very good at “real-world” inputs (missing country, mixed languages, abbreviations), and it provides multiple endpoints that help you build solid UX patterns: autosuggest/typeahead, discover/browse, and geocode/reverse geocode.
HERE Geocoding & Search API pricing
This section summarizes HERE’s typical pricing model for Geocoding & Search: a free tier, then volume-based pricing.
Note about sources: HERE’s official pricing pages may be rendered dynamically depending on region/account. The numbers below are consistent across multiple public references and match commonly reported tiers — but always verify in your HERE account before committing.
HERE typically uses a pay-as-you-go pricing model with a 30,000 requests/month free tier on common plans. After that, the unit price decreases with volume:
| Monthly volume | Price per 1,000 |
|---|---|
| 0 – 30,000 | FREE |
| 30,001 – 5,000,000 | $0.83 |
| 5,000,001 – 10,000,000 | $0.66 |
| 10,000,001+ | Custom |
Prices shown are indicative and commonly reported for Geocoding & Search. Always verify current pricing in your HERE account.
The chart below illustrates how HERE pricing scales with volume using the tiers above:
Cost calculator
Use the following calculator to estimate the monthly cost of your HERE geocoding requests with the tiers above:
Disclaimer: this calculator is for informational purposes only and may not reflect your negotiated discounts, region-specific pricing, or plan-specific conditions.
Rate Limits
HERE’s rate limits are plan-dependent and may vary by product, endpoint, and account.
- Some lower tiers (often described as “Limited” plans) are commonly reported to include daily request caps and requests-per-second (RPS) limits.
- Higher tiers (often described as “Base” plans) typically focus on monthly usage-based billing and may relax strict RPS caps, but you should still expect standard throttling behavior if you burst too aggressively.
When you hit limits: you’ll typically receive HTTP errors (often 429 Too Many Requests). Your integration should implement retries with exponential backoff and request pacing.
License and Terms of Service
HERE’s licensing terms are generally less “map-display restrictive” than some competitors, but they are very explicit about storage/caching and building repositories.
🚫 Key restrictions (storage & scaling)
Repository building is prohibited
- You can’t cache/store location data to build a repository of location assets
- You can’t “scale one request to serve multiple end users” via stored results
Caching is limited
- Caching may be allowed only as specified by caching headers, or
- Limited caching (commonly up to 30 days) may be allowed only to enable/improve an end user’s use
Attribution & separation
- If you overlay your own or third-party data, you must keep data origin distinguishable and provide correct attribution
✅ What you can usually do
- Use HERE geocoding results inside your application for end-user experiences
- Use coordinates in your mapping stack (while respecting terms, attribution, and usage limits)
- Cache results within the permitted scope (headers / limited time / end-user improvement)
Always read the official terms: licensing details matter a lot if your product involves bulk geocoding, data enrichment, or long-term storage.
Learn more in the official documentation:
Practical note for 2026: developer portal migration
HERE has announced that developer.here.com is being shut down by March 16th, 2026 and that users should migrate to the newer HERE portal experience. If you’re starting a new integration in 2026, plan your account setup and documentation bookmarks accordingly.
Conclusion
HERE Geocoding & Search is a strong choice if you want high-quality address resolution and solid POI search, with a generous free tier and typically competitive pricing at scale. The biggest thing to watch is licensing: if your use case requires long-term storage of geocoding results or building a reusable location database, you’ll need to design carefully (and potentially negotiate enterprise terms).
Optimize your geocoding costs: If you’re running multi-provider geocoding or large-scale address cleaning, Coordable can help you maximize accuracy while minimizing costs through intelligent provider selection and address normalization.
**Last updated:** 2026-01-09 | **Updated by:** Coordable | **Sources:** HERE Developer Terms and Conditions, HERE Location Services Coverage Information, Geocoding APIs Pricing Comparison (Bitoff), Free Geocoding APIs List (Ambee)
Disclaimer: This guide is for informational purposes. Always refer to official HERE documentation and your account’s pricing/terms for the most current conditions.