---
title: "Best EV chargers along a route (see module docs)."
method: POST
path: "/v1/charging/along"
tags: ["routing"]
---

# Best EV chargers along a route (see module docs).

`POST /v1/charging/along`

## Request

- Base URL: `https://api.mapmap.ai`
- URL: `https://api.mapmap.ai/v1/charging/along`
- Auth: one of:
  - HTTP bearer
  - API key in query parameter `api_key`

## Request body

- object

## Response `200`

Charge 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

- object

## Other responses

- `400`: Invalid request
- `401`: Missing or invalid API key
- `429`: Quota or rate limit exceeded
- `501`: The charge-point dataset is not enabled (SN_CHARGE_DIR unset)
- `502`: Upstream routing engine failed

---

[API](https://skmtc.dev/mapmap/apis/sn-gateway.md) · [All operations](https://skmtc.dev/mapmap/apis/sn-gateway/llms.txt) · [OpenAPI document](https://skmtc.dev/mapmap/apis/sn-gateway/revisions/2293be8b4c38?raw)