Documentation menu
routing
POST/v1/cameras/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/cameras/along" \
-H "Authorization: Bearer $MAPMAP_KEY" \
-H "Content-Type: application/json" \
-d @request.jsonRequest body
application/json · CamerasAlongRequest
Route shape as polyline6 plus an optional corridor buffer (buffer_m, default 40 m, max 100 m)
| Field | Type | Required | Description |
|---|---|---|---|
| buffer_m | number | no | Corridor half-width in metres; default 40, clamped to at most 100. |
| shape | string | yes | The route shape as a polyline6 string. |
Responses
200Cameras along the route (arc-ordered) and the applied jurisdiction policy
| Field | Type | Required | Description |
|---|---|---|---|
| attribution | string[] | no | Attribution notices for the data actually returned, to display verbatim. Empty when no cameras were returned. Deduplicated and ordered by territory, then by the source's own order. |
| cameras | CameraAlong[] | yes | Cameras within the corridor, arc_m ascending. Always empty in
an omitted jurisdiction. |
| policy | CamerasPolicy | yes | The policy that was applied server-side. |
400Invalid request
401Missing or invalid API key
429Quota or rate limit exceeded
501Camera sidecars are not enabled (SN_CAMERAS_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/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_cameras_along