Documentation menu
POST/v1/charging/along
API key required, sent as Authorization: Bearer snk_… or ?api_key=snk_….
Call it
curl -fsS -X POST "https://api.mapmap.ai/v1/charging/along" \
-H "Authorization: Bearer $MAPMAP_KEY" \
-H "Content-Type: application/json" \
-d @request.jsonRequest body
application/json
EV charge-point search: a route (geometry_polyline6, or origin + destination + costing), an optional connectors filter (type2, ccs, chademo, tesla, type1, domestic, other), min_kw, available_only (needs an availability overlay), max_detour_minutes (default 10, max 120), max_results (default 5, max 25), Valhalla costing_options and an optional top-level adr profile
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, route, max_detour_minutes, filters: {connectors, min_kw, available_only}, candidates: {considered, costed, cap}, coverage: {chargers, evses, countries, sources}, coverage_note (ALWAYS present; an empty results array means none from these operators, never no chargers here), sources[]: {source_id, operator, chargers, coverage_note, licence}, availability: {live, note}, note (only when results is empty, naming which cause applies), results[]: {charger_id, source, operator, name, lat, lon, max_power_kw, connector_standards, evse_count, best_connector, status, status_live, available_now, detour_minutes, detour_km, along_route_position, off_route_m, updated_at}, charging_attribution}. Detours are engine-computed, never crow-fliesError 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_charging_along