Changelog
Some values may only be filled in the future, but are already provided in the Proto for development purposes. See field availability.
30 September 2026 — flexible transfer pricing
Section titled “30 September 2026 — flexible transfer pricing”- Changed: BravoFlex retains its own fare and the following regular public transport leg’s entrance rate. A journey with BravoFlex does not automatically receive a flex-to-public-transport transfer discount.
- Changed: The first-mile flex entrance-rate waiver is restricted to U-OV Flex and HWGO belbus products followed by regular public transport within the eligible 35-minute transfer window. Train boundaries are excluded. The waiver applies to the eligible flex leg, while the following regular leg keeps its entrance rate.
- Client impact: Display the returned
LegPrice.discounts,finalPriceand trip total.
29 September 2026 — flexible line labels
Section titled “29 September 2026 — flexible line labels”- Changed: If a flexible line has no public code,
Line.publicCodenow uses its source line name, falling back toFlexwhen the name is absent. Do not depend on a fixed fallback badge.
23 September 2026 — place names, stop identities and continuation
Section titled “23 September 2026 — place names, stop identities and continuation”Added fields
Section titled “Added fields”| Message | Field / number | Purpose |
|---|---|---|
PlanRequest | fromPlaceName / 29, toPlaceName / 30 | Optional display names for the origin and destination coordinates |
Quay | privateCode / 14 | Stop code associated with the journey |
Quay | stopPlace / 15 | Optional parent stop or station |
StopPlace (new message) | id / 1, name / 2, town / 3, latitude / 4, longitude / 5, transportModes / 6 | Parent identity and presentation; town and coordinates have optional presence |
Keep sending fromPlace and toPlace as coordinates. Display names are not location identifiers. Parent stop data is optional and may be absent.
Breaking semantics and corrected behavior
Section titled “Breaking semantics and corrected behavior”- Breaking semantics:
Quay.quayCode(field 11) is now intended for quay-code context rather than the journey-specific stop code. ReadQuay.privateCodefor journey/pricing context andQuay.idfor the returned quay identity. The codes may be empty; do not derive a quay ID from them. - Changed:
Quay.situationscontains alerts affecting the quay when available. - Changed:
TransitLeg.staySeateddescribes the interchange following that leg. Place “Stay on board” at the end of that transit leg before its continuation.