Skip to content

50,000 free calls a month, card-free. Get an API key →

Log inGet an API key
Documentation menu
docs / api / post-locate
routing

POST/locate

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

Call it

bash
curl -fsS -X POST "https://api.mapmap.ai/locate" \
  -H "Authorization: Bearer $MAPMAP_KEY" \
  -H "Content-Type: application/json" \
  -d @request.json

Request body

application/json

Valhalla locate request JSON: locations, costing, optional costing_options, verbose (default false) and units

The OpenAPI document declares this body as a free-form JSON object with no field list, so there is nothing here to generate a table from. The prose above is what the gateway states about it; the raw document is the authority.

Responses

200One entry per input location: the closest edges (way id, correlated point, side of street, percent along) and, in verbose mode, nodes with a dense administrative/access/geometry attribute tree. A location with no nearby graph edges (open sea, an unmapped area) answers an entry with empty edges/nodes arrays, never an error
400Invalid request
401Missing or invalid API key
429Quota or rate limit exceeded
501SN_ROUTING_ENGINE=graphhopper: GraphHopper has no locate service
502Upstream routing engine failed

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

Also under routing

POST /centroidPOST /isochronePOST /matrixPOST /optimisePOST /optimise/replanPOST /routePOST /route/alongPOST /route/progressPOST /route/reportGET /route/v1/{profile}/{coordinates}POST /trace_attributesPOST /trace_routePOST /v1/cameras/alongPOST /v1/charging/alongPOST /v1/clusterPOST /v1/ev/planPOST /v1/fuel/alongPOST /v1/incidents/alongPOST /v1/jobs/matrixPOST /v1/jobs/optimisePOST /v1/jobs/replanPOST /v1/weather/alongGET /v1/zones

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