How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Need help?

Contact us
HERE

HERE Route Matching V8 API

Match GPS traces onto the most probably driven path

Documentation Provider Profile APIs.io OpenAPI GitHub

HERE Route Matching V8 API is one of 139 APIs that HERE publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Route Matching V8. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and an API reference.

This API exposes 3 operations across 2 paths, and defines 32 schemas. It is described by OpenAPI 3.2.0, at version 8.3.3.

Requests are made against a single base URL, https://routematching.hereapi.com.

3 operations 2 paths 32 schemas 1 GET2 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
8.3.3
Base URL
https://account.api.here.com
Authentication
API Key, HTTP Bearer
License
HERE Documentation License
Terms of Service
View terms
Resource Areas
1

Authentication & Security 2

HERE Route Matching V8 API declares 2 security schemes for authenticating requests. An API key is passed in the query as apiKey (apiKey). It accepts HTTP bearer tokens (JWT) (bearerTokenAuth). By default, every request must be authenticated.

  • apiKey — A key generated specifically to authenticate API requests. For more information on how to get an API key, see [Identity and Access Management Developer Guide](…
  • bearerTokenAuth — A token obtained from a separate endpoint using client credentials and an OAuth 1.0a HMAC-SHA256 signed request. For more information on how to get a bearer to…

Paths & Operations 3

Across 2 paths, the API surfaces 3 operations — 1 GET, 2 POST. Each is listed below with its method, path, parameters, and response codes.

Route Matching V8 3

Match GPS traces onto the most probably driven path

GET
/v8/match/routelinks
Match GPS traces to get the most probably driven path.
HERERouteMatchingV8APIMatchRouteV8compatibilityToV2GET 83 params → 200
POST
/v8/match/routelinks
Match GPS traces to get the most probable driven path.
HERERouteMatchingV8APIMatchRouteV8compatibilityToV2POST 90 params body → 200
POST
/v8/maps/overlays/upload
Submit an overlay map for customized route matching.- Deprecated
HERERouteMatchingV8APIOverlayUploadV8 18 params body → 200

Schemas 32

The contract defines 32 schemas that model the data the API accepts and returns. The most detailed are VehicleSpecification (33 properties), TracePoint (31 properties), TurnByTurnManeuver (17 properties), Leg (16 properties). Each schema is shown below with its type and property counts.

Leg
object
one leg traverses between two mandatory stopover waypoints
16 properties
KeyValue
object
requested PDE layer attributes for the link
2 properties
Response
object
Calculate route response
BaseResponse
object
TSystem
object
3 properties
JsonSerializable
object
RouteTollItem
object
routeTollItems are a list of all toll cost items (for rollups=none).
12 properties
RouteMode
object
from the request
3 properties
ResponseIssue
object
Warnings that are either globally for the request or apply to the first route alternative.
11 properties
Route
object
Route alternatives. The first route alternative has the minimum cost.
13 properties
CurrencyAmount
object
totalCost is the sum of all cost elements.
6 properties
TollStructure
object
Toll booth(s)/bridge(s) at start and/or end of this toll section
7 properties
BoundingBox
object
2 properties
Costs
object
3 properties
SearchMetaResponse
object
3 properties
WayPoint
object
TollCost
object
toll fee alternatives, depending on vehicle type, time of day, day of week, month, payment method, pass, transponder...
13 properties
OverlaySubmitResponse
object
3 properties
TracePoint
object
31 properties
VehicleSpecification
object
33 properties
TCResponse
object
the requested toll cost rollups
5 properties
MatchedVehicleType
object
Most probable vehicle type(s), only for route match mode. Only returned if the input trace contains speed or timestamp information.
3 properties
CostDetails
object
6 properties
Summary
object
7 properties
Pass
object
7 properties
Coordinate
object
2 properties
Maneuver
object
14 properties
RoadName
object
2 properties
TurnByTurnManeuver
object
17 properties
ManeuverPosition
object
2 properties
Link
object
14 properties
RouteSummaryByCountry
object
6 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

here-route-matching-v8-api-openapi.yml Raw ↑

Other APIs HERE publishes across the network.

HERE Geocoding and Search API
AE Profile APIs.io
HERE Autosuggest API
AE Profile APIs.io
HERE Tour Planning API
AE Profile APIs.io
HERE Public Transit API
AE Profile APIs.io
HERE Destination Weather API
AE Profile APIs.io
HERE Map Tile API
AE Profile APIs.io
HERE Map Image API
AE Profile APIs.io
HERE Tracking API
AE Profile APIs.io
HERE Positioning API
AE Profile APIs.io
HERE Parking API
AE Profile APIs.io
HERE Platform Data API
AE Profile APIs.io
HERE HD Live Map
AE Profile APIs.io
#Route Matching V8
← Back to H APIs
API Details
ID
here:here-route-matching-v8-api
Base URL
https://account.api.here.com
Docs
https://docs.here.com/identity-and-access-management/reference
Provider
HERE
APIs.io →  GitHub →
Explore more
All APIs Providers APIs.io Network
Work with this as data

Every API here is available over the API and to AI agents over MCP. APIs is not yet its own endpoint on the v1 API. Reach this content through network search and the tag graph, or the MCP server below.

Installs https://mcp.apievangelist.com/mcp in Claude, Cursor, VS Code and the rest — one button, every client.

MCP tools for apis
4 tools reach this content
  • search_api_evangelistSearch every content type across the network at once.
  • find_relatedThe shared-tag relevance graph — what else covers this.
  • get_tagEverything one tag labels, across all content types.
  • guide_topicPRO — a curated bundle for a topic: area, guidance, rules, papers, stories, services.
All tools & prompts
Call it yourself
curl for this page
Search the network for this 
curl "https://api.apievangelist.com/v1/search?q=here-route-matching-v8-api&limit=10"
Everything under a tag 
curl "https://api.apievangelist.com/v1/tags/here-route-matching-v8-api"

Discovery needs no key. Full bodies and the synthesis endpoints are Pro.

Get an API key

Free tier, no email required. Sign in with whichever identity you already have.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have. Your account

Where this information came from

This is an independent, third-party profile of HERE Route Matching V8 API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.