Documentation menu
routing
POST/v1/incidents/along
API key required, sent as Authorization: Bearer snk_… or ?api_key=snk_….
Call it
bash
curl -fsS -X POST "https://api.mapmap.ai/v1/incidents/along" \
-H "Authorization: Bearer $MAPMAP_KEY" \
-H "Content-Type: application/json" \
-d @request.jsonRequest body
application/json · IncidentsAlongRequest
Route shape as polyline6 plus an optional corridor buffer (buffer_m, default 60 m, max 500 m)
| Field | Type | Required | Description |
|---|---|---|---|
| buffer_m | number | no | Corridor half-width in metres; default 60, clamped to at most 500. |
| shape | string | yes | The route shape as a polyline6 string. |
Responses
200Incidents along the route (arc-ordered) and every configured source's coverage metadata
| Field | Type | Required | Description |
|---|---|---|---|
| attribution | string[] | no | Attribution notices for the sources actually configured, to display verbatim. |
| incidents | IncidentAlong[] | yes | Incidents within the corridor, arc_m ascending. |
| sources | IncidentSourceMetaOut[] | yes | Every configured source's coverage metadata — present even when
incidents is empty. |
400Invalid request
401Missing or invalid API key
429Quota or rate limit exceeded
501Incident data is not enabled (SN_INCIDENTS_DIR unset)
Error bodies follow the shared problem model documented on API conventions.
Also under routing
POST /centroidPOST /isochronePOST /locatePOST /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/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_incidents_along