Documentation menu
POST/route/progress
API key required, sent as Authorization: Bearer snk_… or ?api_key=snk_….
Call it
curl -fsS -X POST "https://api.mapmap.ai/route/progress" \
-H "Authorization: Bearer $MAPMAP_KEY" \
-H "Content-Type: application/json" \
-d @request.jsonRequest body
application/json
Where a vehicle is against its plan, statelessly. The plan as geometry_polyline6, or origin + destination + costing (the route-input contract POST /v1/fuel/along accepts), plus current_position {lat, lon}; optional recent_trace (up to 100 points, oldest first: switches snapping from geometric projection to engine map matching), off_route_threshold_m (default 50), Valhalla costing_options and a top-level adr profile. NO POSITIONS ARE STORED: the request is answered and forgotten
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
{costing, stateless: true, plan: {length_m, source, duration_s, distance_m}, position: {input, snapped, method, along_m}, progress: {fraction, travelled_m, plan_remaining_m}, off_route, off_route_m, off_route_threshold_m, arrived, remaining: {distance_m, duration_s, method}, eta: {duration_s, arrival_estimate_utc, traffic}}. method is projection (single fix, geometric) or map_matched (a recent_trace was matched through the engine). remaining is a fresh engine search from where the vehicle is to the plan's final point, so it can differ from progress.plan_remaining_m; eta.traffic carries the same coverage/confidence provenance POST /route reportsrecent_trace, or a plan geometry with fewer than two pointsError bodies follow the shared problem model documented on API conventions.
Also under routing
Generated from https://api.mapmap.ai/openapi.json on 2026-09-17 · operationId post_route_progress