GET/directions/v5/{user}/{profile}/{coordinates}

API key required, sent as Authorization: Bearer snk_… or ?api_key=snk_….

Call it

bash

curl -fsS -X GET "https://api.mapmap.ai/directions/v5/{user}/{profile}/{coordinates}" \
  -H "Authorization: Bearer $MAPMAP_KEY"

Parameters

Name	In	Required	Description
user	path	yes	`mapbox` or `mapmap`
profile	path	yes	`driving`, `driving-traffic` (served as `driving`: traffic-aware times cover the England strategic road network only), `walking`, `cycling` or `truck` (MapMap extension, premium)
coordinates	path	yes	`lon,lat` pairs separated by `;`
access_token	query	no	Your MapMap key (`snk_...`), accepted here as Mapbox clients send it; `api_key` and a bearer header work too
alternatives	query	no	Return up to three alternative routes
annotations	query	no	Comma-separated: `distance`, `duration`, `speed` (each manoeuvre's engine length and time spread over its segments by length) and `maxspeed`. `congestion`, `congestion_numeric`, `closure` and `state_of_charge` are refused with a 400 naming the supported set
geometries	query	no	`polyline` (default), `polyline6` or `geojson`
overview	query	no	`simplified` (default), `full` or `false`
steps	query	no	Turn-by-turn steps
language	query	no	BCP 47 instruction language
voice_instructions	query	no	Mapbox-shaped `voiceInstructions` on each step (metric units)
banner_instructions	query	no	Mapbox-shaped `bannerInstructions` on each step
exclude	query	no	`toll`, `motorway`, `ferry`, `tunnel`: hard exclusions, so an unavoidable one answers `NoRoute` where Mapbox would return a violating route
depart_at	query	no	Local departure time, `YYYY-MM-DDThh:mm`
approaches	query	no	`curb` or `unrestricted` per coordinate, `;` separated

Responses

200Mapbox Directions response: code, routes (each with weight_name: "duration"), waypoints and uuid (the request id). NoRoute and NoSegment also answer 200 with that code and empty routes, as Mapbox documents

400{code, message}: InvalidQuery or InvalidValue, including any Mapbox option MapMap does not honour (the message names the supported set). Not billed

401Missing or invalid key

403A browser (maps) key: routing needs a full key

404ProfileNotFound

429Quota or rate limit exceeded

Error bodies follow the shared problem model documented on API conventions.

Also under mapbox-compat

GET /directions-matrix/v1/{user}/{profile}/{coordinates}GET /geocoding/v5/mapbox.places/{query}GET /isochrone/v1/{user}/{profile}/{coordinates}GET /optimized-trips/v1/{user}/{profile}/{coordinates}GET /search/geocode/v6/forward GET /search/geocode/v6/reverse

Generated from https://api.mapmap.ai/openapi.json on 2026-10-17 · operationId get_directions