GraphHopper Directions API logo

GraphHopper Directions API

GraphHopper Directions API

GraphHopper provides routing, matrix, isochrone, geocoding, map matching, clustering, and VRP endpoints in one Directions API.

Visit site ↗Health checked 9h ago
Use it when

Covers route, matrix, vrp, and match in one API

Watch for

The surface is broad, so you need to decide which sub-API you actually need

First check

Validate your api_key against /route or /geocode first, then expand to /matrix, /isochrone, /match, or /vrp. For async job flows, pay attention to the calculate/solution endpoint pairs.

Auth
api_key
CORS
Yes
HTTPS
Yes
Signup
Required
Latency
1024 ms
Protocol
REST
Pricing

Uptime · 30-day window

Probes: 1Uptime: 100%Avg latency: 1024ms
01

About this API

This is more than a single route endpoint: GraphHopper bundles Routing, Matrix, Isochrone, Map Matching, Cluster, and VRP operations into one navigation-compute surface. The spec exposes paths such as "/cluster", "/cluster/calculate", "/cluster/solution/{jobId}", and "/geocode" and names feature groups like "Route Optimization API", "Routing API", and "Matrix API".

Those concrete resources are useful when you need to calculate turn-by-turn routes, generate matrix or vrp solutions, or run map matching or isochrone analysis on location data. The OpenAPI document names security schemes such as "api_key".

The surface is broad, so you need to decide which sub-API you actually need Some job-oriented flows require polling a solution endpoint

02

What you can build

  • 1Calculate turn-by-turn routes
  • 2Generate matrix or VRP solutions
  • 3Run map matching or isochrone analysis on location data
03

Strengths & limitations

Strengths

  • Covers route, matrix, vrp, and match in one API
  • Uses straightforward api_key authentication
  • Includes async calculate/solution job flows

Limitations

  • The surface is broad, so you need to decide which sub-API you actually need
  • Some job-oriented flows require polling a solution endpoint
04

Example request

Generic template — replace <endpoint> with the real path from the docs.
curl https://www.graphhopper.com/<endpoint> \
  -H "Authorization: Bearer $API_KEY"
# Some providers use X-Api-Key instead — verify in the docs.
05

Getting started

Validate your api_key against /route or /geocode first, then expand to /matrix, /isochrone, /match, or /vrp. For async job flows, pay attention to the calculate/solution endpoint pairs.

06

Technical details

CORS: YesHTTPS: YesSignup: YesOpen source: No
Auth type
api_key
Pricing
unknown
Protocols
REST
Response time
1024 ms
Last health check
5/12/2026, 7:37:38 AM
07

Tags