Matrix API


The endpoint is[version]/matrix

You get an example response for a 3x3 matrix looks via:

curl ",11.588051&point=50.241935,10.747375&point=50.118817,11.983337&type=json&vehicle=car&debug=true&out_array=weights&out_array=times&out_array=distances&key=[YOUR_KEY]"


Matrix Example

The Matrix API is part of the GraphHopper Directions API and with this API you can calculate many-to-many distances, times or routes a lot more efficient than calling the Routing API multiple times.

In the Routing API we support multiple points, so called 'via points', which results in one route being calculated. The Matrix API results in NxM routes or more precise NxM weights, distances or times being calculated but is a lot faster compared to NxM single requests. The most simple example is a tourist trying to decide which pizza is close to him instead of using beeline distance she can calculate a 1x4 matrix. Or a delivery service in the need of often big NxN matrices to solve vehicle routing problems. E.g. the GraphHopper Route Optimization API uses the Matrix API under the hood to achieve this.

Some other use case scenarios for the Matrix API:

API Clients and Examples

See the clients section in the main document and live examples.


The Matrix API calculates the well known distance-matrix for a set of points, i.e. it calculates all the distances between every point combination. But we do not stop there, we also offer a time-, weight- and route-matrix. The weight-matrix can be used as raw input for e.g. a vehicle routing problem (VRP) and is more precise than a time- or distance-matrix. E.g. for bike routes the actual weight of a route (e.g. the "beauty") is what you want to decide if a route is 'better' and not always the taken time or distance.

A simple illustration for a 3x3 matrix with identical from and to points:

- to_point1 to_point2 to_point3
from_point1 0 1->2 1->3
from_point2 2->1 0 2->3
from_point3 3->1 3->2 0

A simple illustration for a 1x3 matrix with different start- and end-points:

- to_point1 to_point2 t_point3
from_pointA A->1 A->2 A->3

For every route 1->2, 1-3, ... or A->1,A->2,A->3 you can return only the weight, the time and the distance. To calculate full routes you can use the Routing API which also has a lot of different parameters.


All official parameters are shown in the following table

Parameter Default Description
point - Specifiy multiple points for which the weight-, route-, time- or distance-matrix should be calculated. In this case the starts are identical to the destinations. If there are N points, then NxN entries will be calculated. The order of the point parameter is important. Specify at least three points. Cannot be used together with from_point or to_point. Is a string with the format latitude,longitude.
from_point - The starting points for the routes. E.g. if you want to calculate the three routes A->1, A->2, A->3 then you have one from_point parameter and three to_point parameters. Is a string with the format latitude,longitude.
to_point - The destination points for the routes. Is a string with the format latitude,longitude.
out_array weights Specifies which arrays should be included in the response. Specify one or more of the following options 'weights', 'times', 'distances'. To specify more than one array use e.g. out_array=times&out_array=distances. The units of the entries of distances are meters, of times are seconds and of weights is arbitrary and it can differ for different vehicles or versions of this API.
vehicle car The vehicle for which the route should be calculated. Other vehicles are listed here for the details.
debug false If true, the output will be formated.

Limits and Counts

The cost for one request depends on the number of locations and is documented here.

One request should not exceed the Matrix API location limit depending on the package, see the pricing in our dashboard.

JSON Output

Keep in mind that some attributes which are not documented here can be removed in the future - you should not rely on them! In the following example 4 points were specified and out_array=distances&out_array=times&out_array=weights&debug=true:

  "weights" : [ [ 0.0, 449.753, 298.715, 664.113 ], [ 447.935, 0.0, 290.489, 543.242 ], [ 293.111, 283.954, 0.0, 452.725 ], [ 658.792, 537.769, 451.928, 0.0 ] ],
  "times" : [ [ 0, 5831, 3873, 8610 ], [ 5808, 0, 3766, 7043 ], [ 3800, 3681, 0, 5869 ], [ 8541, 6972, 5859, 0 ] ],
  "distances" : [ [ 0, 119124, 79156, 199907 ], [ 108691, 0, 63641, 142487 ], [ 79044, 71409, 0, 132215 ], [ 198852, 141322, 131953, 0 ] ],
  "info" : {
    "copyrights" : [ "GraphHopper", "OpenStreetMap contributors" ]

The JSON result contains the following structure:

JSON path/attribute Description
times The time matrix for the specified points in the order [[from1->to1, from1->to2, ...], [from2->to1, from2->to2, ...], ...]. The times are in seconds.
distances The distance matrix for the specified points in the same order as the time matrix. The distances are in meters.
weights The weight matrix for the specified points in the same order as the time matrix. The weights for different vehicles can have a different unit but the weights array is perfectly suited as input for Vehicle Routing Problems as it is currently faster to calculate.
info.copyrights Attribution according to our documentation is necessary if no white-label option included.

HTTP POST request

The GET request has an URL length limitation, which hurts for many locations per request. In those cases use a HTTP POST request with JSON data as input. The only parameter in the URL will be the key which stays in the URL. Both request scenarios are identically except that all singular parameter names are named as their plural for a POST request. For example point=10,11&point=20,22 will be converted to the following JSON points array:

{ "points": [[11,10], [22,20]] }

Note that also the order changes to [longitude,latitude] similar to a GeoJson. All effected parameters are: points, from_points and to_points.

Also out_array has to be named out_arrays in a POST request.

curl example with a JSON as input:

curl -X POST -H "Content-Type: application/json" "[YOUR_KEY]" -d '{"elevation":false,"out_arrays":["weights"],"from_points":[[-0.087891,51.534377],[-0.090637,51.467697],[-0.171833,51.521241],[-0.211487,51.473685]],"to_points":[[-0.087891,51.534377],[-0.090637,51.467697],[-0.171833,51.521241],[-0.211487,51.473685]],"vehicle":"car"}'

JSON response:

"info":{"copyrights":["GraphHopper","OpenStreetMap contributors"]}

Batch Matrix API

The Batch Matrix API allows using matrices with more locations and works asynchronously - similar to our Route Optimization API: * Create a HTTP POST request against /matrix/calculate and add the key in the URL: /matrix/calculate?key=[YOUR_KEY]. This will give you the job_id from the response json like { "job_id": "7ac65787-fb99-4e02-a832-2c3010c70097" } * Poll via HTTP GET requests every second against /matrix/solution/[job_id]

Here are some full examples via curl:

$ curl -X POST -H "Content-Type: application/json" "[YOUR_KEY]" -d '{"points":[[13.29895,52.48696],[13.370876,52.489575],[13.439026,52.511206]]}'

Pick the returned job_id and use it in the next GET requests:

$ curl -X GET "[YOUR_KEY]"

When the calculation is finished (status:finished) the JSON response will contain the full matrix JSON under solution:

$ curl -X GET "[YOUR_KEY]"
{"solution":{"weights":[[0.0,470.453,945.414],[503.793,0.0,580.871],[970.49,569.511,0.0]],"info":{"copyrights":["GraphHopper","OpenStreetMap contributors"]}},"status":"finished"}

Please note, if an error occured while calculation the JSON will not have a status but contain directly the error message e.g.:

{"message":"Cannot find from_points: 1","hints":[{...}]}

HTTP Error codes

See more details in the overview