HERE Location Services, implemented
Placematic is an official HERE reseller and Gold Partner. We issue production API keys, hold the contract, and write the guidance below from systems we have shipped since 2016. Start with a request that returns200.
No key yet? Request one — issued within one business day, no credit card, no demo call. Placematic USA LLC is the contracting party. You never open a HERE account.
Start here
Getting Started
Platform overview, API keys, authentication, and how HERE pricing actually works.
Guides
Truck routing, distance matrices, batch geocoding, and migrating off Google Maps.
Use Cases
Reference architectures for fleet and ELD platforms, delivery zones, and retail networks.
Comparisons
HERE against Google, TomTom, and Mapbox — including where they beat HERE.
Cost optimization patterns
Learn how batching, caching, pre-computation and choosing the right HERE API can reduce location API costs.
MCP Server
Learn about a Model Context Protocol endpoint that exposes the Placematic Spatial API to AI agents as callable tools.
What this documentation covers
HERE maintains the parameter tables and response schemas. We link to them. What we write is the layer around the reference: Which API answers your question. Routing, Distance Matrix, and Tour Planning look interchangeable and are not. Building a matrix from a loop of routing calls is the most expensive architectural mistake in this domain. What it will cost. Per-1,000 rates are close across vendors. Your bill is set by call mix, volume tier, and whether you batched. We show you how to forecast it before you sign anything. How teams get it wrong.transportMode=truck selects a routing engine. It does not supply your vehicle’s dimensions. Omit them and HERE returns a route, without warning, that a 4.1m trailer cannot physically drive.
When to use something else. For consumer place discovery, business hours, and reviews, Google’s data is better and you should keep it. Under roughly 10k calls a month, migration is a rounding error you will spend a quarter chasing.
Featured guides
Truck Routing
Physical constraints as first-class inputs — and the trap geometry that proves your integration applies them.
HERE Pricing Explained
Call volume versus asset-based pricing, and how to model a bill you can defend to finance.
Choosing the Right HERE APIs
A decision path by the question your system asks, not by product name.
Migrating from Google Maps
Endpoint mapping, sequencing, and validating route quality during cutover.
Who builds on this
Placematic has been a HERE Gold Partner since 2016, deploying HERE into production routing engines, ELD platforms, and field operations tools. Every page here comes from an integration we shipped, including the ones that went badly the first time. See how teams run this in production: Placematic case studiesOur implementation philosophy
A production location system should not call an external API for every decision. Use HERE where fresh routing, traffic, geocoding or map data matters. Cache, batch and materialize everything else.Need production keys?
Placematic helps engineering teams select the right HERE APIs, forecast usage, migrate from Google Maps, and reach production. One contract, one invoice, no direct HERE account.Request API keys
One business day. No credit card. No demo call required.