Skip to content
Log inGet an API key
Documentation menu
docs / api / post-v1-charging-along
routing

POST/v1/charging/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/charging/along" \
  -H "Authorization: Bearer $MAPMAP_KEY" \
  -H "Content-Type: application/json" \
  -d @request.json

Request 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

200Charge points matching the filters within the detour budget, most powerful first: {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 (the best of the standards the request filtered on, the site's best when it filtered on none), status, status_live, available_now, detour_minutes, detour_km, along_route_position, off_route_m, updated_at}, say, charging_attribution}. say is the whole answer as one short spoken line, present on every response including an empty one, and it scopes its claim to the operators this deployment covers. Detours are engine-computed, never crow-flies
400Invalid request
401Missing or invalid API key
429Quota or rate limit exceeded
501The charge-point dataset is not enabled (SN_CHARGE_DIR unset)
502Upstream routing engine failed

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/clusterPOST /v1/errands/planPOST /v1/ev/planPOST /v1/fuel/alongPOST /v1/incidents/alongPOST /v1/jobs/coveragePOST /v1/jobs/matrixPOST /v1/jobs/optimisePOST /v1/jobs/replanPOST /v1/route/heritagePOST /v1/route/observationsPOST /v1/weather/alongGET /v1/zones

Generated from https://api.mapmap.ai/openapi.json on 2026-11-01 · operationId post_charging_along