Route Optimization OptiFlow API - Api Changes 1.35.0 (24.11.2025)

[Bernd Welter]

Api	VarVersion	Type	Date	Description
Route Optimization OptiFlow API	1.35.0	FEATURE	24.11.2025	Breaks are no longer scheduled between tasks at the same stop. Therefore there are no more breaks at Task and Appointment.

Let me comment on this:

• An application based on 1.34 or before won't raise an error with the 1.35 backend
• I had to update my client application when I replaced the 1.34 client classes with the 1.35 versions (remove all handling of .Breaks)
• As long as you haven't stored the 1.34 results cluding breaks in your database and then want to deserialize them based on 1.35 it should not ae issues.

If anyone of you runs into issues after the update get back to us.

Bend

[Bernd Welter]

So here comes some "learning" from a player who probably wishes he had known this (had some stress today): feel free to port this info to your brain

• The player created a business logic based on a manual JSON string handling which expected the element breaks as it was defined in 1.34 -though this was an OPTIONAL element and returned as

  Code: Select all

  "appointments":[
   {
     "breaks": [],
     "waitingDuration": 0,...
   }...
  ]
  

• When we removed the element according to the spec below... the response now no longer returns a property "breaks"...

  Code: Select all

  "appointments":[
   {
     "waitingDuration": 0,...
   }...
  ]
  

  When he tried to access this element he faced some "doesn't exist!" error...

Therefore please always remember:

THE MACHINE OPEN API SPEC is the reference! - If we mention such a topic in the release notes take a few seconds to derive the consequences for your application!