Charging Stops

The most common planner scenario: a route longer than one battery charge. You submit a single section from A to B, and the optimizer decides where to charge, for how long, and to which state of charge — trading off charging speed (charging is fastest at low SoC), detours, and mandatory driver rest so that total tour time is minimal. This example plans Berlin → Frankfurt (546 km) for a truck starting at 80% battery. The request needs only the route, the payload, and a station filter (poi_info); everything about charging is decided by the optimizer.

Request

curl -X POST "https://api.fryte.com/planner/v2?corridor=8000" \
  -H "Authorization: Bearer <your-token>" \
  -H "Content-Type: application/json" \
  -d '{
    "vehicle_id": "010160700001",
    "battery_level_start": 0.8,
    "section_list": [
      {
        "start_pos": [52.5200, 13.4050],
        "stop_pos": [50.1109, 8.6821],
        "payload_kg": 19300
      }
    ],
    "poi_info": {
      "min_kW": 150,
      "connector_type": ["CCS"]
    }
  }'

import requests

response = requests.post(
    "https://api.fryte.com/planner/v2",
    params={"corridor": 8000},
    headers={"Authorization": "Bearer <your-token>"},
    json={
        "vehicle_id": "010160700001",
        "battery_level_start": 0.8,
        "section_list": [
            {
                "start_pos": [52.5200, 13.4050],
                "stop_pos": [50.1109, 8.6821],
                "payload_kg": 19300,
            }
        ],
        "poi_info": {
            "min_kW": 150,
            "connector_type": ["CCS"],
        },
    },
)
print(response.json())

const response = await fetch("https://api.fryte.com/planner/v2?corridor=8000", {
  method: "POST",
  headers: {
    "Authorization": "Bearer <your-token>",
    "Content-Type": "application/json",
  },
  body: JSON.stringify({
    vehicle_id: "010160700001",
    battery_level_start: 0.8,
    section_list: [
      {
        start_pos: [52.5200, 13.4050],
        stop_pos: [50.1109, 8.6821],
        payload_kg: 19300,
      },
    ],
    poi_info: {
      min_kW: 150,
      connector_type: ["CCS"],
    },
  }),
});
const data = await response.json();
console.log(data);

using var client = new HttpClient();
client.DefaultRequestHeaders.Add("Authorization", "Bearer <your-token>");

var json = """
{
    "vehicle_id": "010160700001",
    "battery_level_start": 0.8,
    "section_list": [
        {
            "start_pos": [52.5200, 13.4050],
            "stop_pos": [50.1109, 8.6821],
            "payload_kg": 19300
        }
    ],
    "poi_info": {
        "min_kW": 150,
        "connector_type": ["CCS"]
    }
}
""";

var response = await client.PostAsync(
    "https://api.fryte.com/planner/v2?corridor=8000",
    new StringContent(json, System.Text.Encoding.UTF8, "application/json")
);
var result = await response.Content.ReadAsStringAsync();
Console.WriteLine(result);

Response

{
  "qualification": "Driveable",
  "battery_level_start": 0.8,
  "battery_level_end": 0.213,
  "sections": [
    {
      "start_pos": [52.52, 13.405, 0.80],
      "stop_pos": [50.886, 11.846, 0.599],
      "polyline": "BlXm6xgK...",
      "poi_summary": {
        "id": 0,
        "name": "Pfalzwerke",
        "address": "Rodaer Straße 72",
        "coordinate_lat": 50.886,
        "coordinate_lon": 11.85,
        "power_available_kW": 200.0,
        "energy_kWh": 180.0,
        "charge_time_min": 60.0,
        "service_time_min": 63.0,
        "arrival_time": "2026-05-04T11:25:00Z",
        "sec_length_km": 240.407,
        "sec_duration_min": 204.942,
        "sec_energy_consumption_kWhkm": 1.247,
        "start_soc": 0.30,
        "stop_soc": 0.60,
        "additional_stops": true,
        "alternatives": [],
        "amenities": [],
        "bookable": false,
        "location_id": "81fe2c7c-8f00-11f0-b171-42010aa400b8"
      }
    },
    "... 2 more charging stop sections ...",
    {
      "start_pos": [50.644, 8.99, 0.32],
      "stop_pos": [50.111, 8.682, 0.213],
      "polyline": "BlX4rj1J...",
      "poi_summary": {
        "id": 0,
        "name": "Destination",
        "address": "See Destination",
        "coordinate_lat": 50.111,
        "coordinate_lon": 8.682,
        "power_available_kW": 0,
        "energy_kWh": 0,
        "charge_time_min": 0,
        "service_time_min": 0,
        "arrival_time": "2026-05-04T17:23:01Z",
        "sec_length_km": 77.448,
        "sec_duration_min": 63.509,
        "sec_energy_consumption_kWhkm": 0.831,
        "start_soc": 0.213,
        "stop_soc": 0.213,
        "additional_stops": false,
        "alternatives": null,
        "amenities": [],
        "bookable": false,
        "location_id": null
      }
    }
  ]
}

What the optimizer did

The optimizer inserted 3 charging stops, splitting the single input section into 4 response sections. Each section ends at a stop described by its poi_summary:

charge_time_min is the pure charging time; service_time_min additionally contains the connecting and parking overhead — the difference is the fixed per-stop overhead.
start_soc / stop_soc are the battery levels when arriving at and leaving the stop. The truck arrives at the first charger at 30%, charges to 60%, and reaches Frankfurt with 21%.
alternatives lists nearby stations you can swap in manually; additional_stops indicates that alternatives exist.
The third coordinate of start_pos / stop_pos is the SoC at that point of the route.

Depending on the route, the time-optimal plan can contain very short top-up stops. If those are operationally undesirable for your fleet, set a floor with min_charge_duration_min.

Getting Started

Example Routes

Endpoints

Request

Response

What the optimizer did

​Request

​Response

​What the optimizer did

Request

Response

What the optimizer did