Skip to content

Changelog

Some values may only be filled in the future, but are already provided in the Proto for development purposes. See field availability.

  • Added: EstimatedCall.scheduledQuay (field 13) contains the originally scheduled quay. expectedQuay contains the quay to use for boarding or alighting, including realtime changes. Both are supplied for boarding, alighting and intermediate calls; they are equal when there is no quay change.
  • Breaking for JSON clients: EstimatedCall.quay is renamed to expectedQuay. Update calls such as fromEstimatedCall.quay to fromEstimatedCall.expectedQuay. The binary field number remains 1, so existing Protobuf clients continue to receive the effective quay through their quay property. Regenerate clients to access both quays.
  • Deprecated: aimedPlatform and expectedPlatform. Use scheduledQuay.publicCode and expectedQuay.publicCode for scheduled and expected platform labels. The deprecated fields continue to carry those labels during the transition.
  • Changed: A quay change can include a different ID, coordinates and platform label. Use expectedQuay for the boarding/alighting location and scheduledQuay to show what changed. When the expected quay has no platform label, display it as unavailable rather than substituting the scheduled label.
  • Changed: Station-derived Quay.quayCode values use NL:Q:<stationCode>_<platform> instead of NL:CHB:Quay:<stationCode>_<platform>. Use Quay.id for quay identity rather than constructing an ID from this code.

The downloadable result schema already includes these upcoming fields. Current responses may still use quay and may not include scheduledQuay. See the quay reference for migration guidance.

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, finalPrice and 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.publicCode now uses its source line name, falling back to Flex when 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”
MessageField / numberPurpose
PlanRequestfromPlaceName / 29, toPlaceName / 30Optional display names for the origin and destination coordinates
QuayprivateCode / 14Stop code associated with the journey
QuaystopPlace / 15Optional parent stop or station
StopPlace (new message)id / 1, name / 2, town / 3, latitude / 4, longitude / 5, transportModes / 6Parent 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: Quay.quayCode (field 11) is now intended for quay-code context rather than the journey-specific stop code. Read Quay.privateCode for journey/pricing context and Quay.id for the returned quay identity. The codes may be empty; do not derive a quay ID from them.
  • Changed: Quay.situations contains alerts affecting the quay when available.
  • Changed: TransitLeg.staySeated describes the interchange following that leg. Place “Stay on board” at the end of that transit leg before its continuation.