Important change in breaks handling within v1.35/1.36/1.37

[Bernd Welter]

Here's also some important remark for those who deal with breaks returned in the response and who use an API call based on v1.35 or before.

• Version 1.36.0 | 2025-12-11 : Feature: Added support for taking a break during charging.
• Version 1.35.0 | 2025-11-24 : Feature: Breaks are no longer scheduled between tasks at the same stop. Therefore there are no more breaks at Task and Appointment.

As you can see from the API changes there's been some impact in the way how we model breaks in the response.

Now with v1.36 we invented a new Breaks-collection at the stops and though the current 1.36 API doc says

breaks
Array of objects (Break)
Indicates when a break is taken at the current stop. A break can only take place during charging.

we have to implement an important internal move which could shift a break from the "approach.breaks" collection to the "stop.breaks" collection - even if there's no charging involved.

This also means that the description of the "stop.breaks" will change with one of the next versions.

We strongly recommend that you already prepare your existing break handling for this new 1.36 stops.break collection - though this might feel like "learning to swim on land".

Bernd