Skip to content
RezRoute

Changelog

What has changed.

This page records changes to the connection that a sales channel or an operator can observe, and the milestones that a reviewer would want dated.

Last updated 24 October 2026.

Entries

  1. Added

    First supplier connected through self-mapping

    The first supplier was connected to GetYourGuide through self-mapping on 21 October 2026.

  2. Added

    GetYourGuide certification

    GetYourGuide certified this connection on 20 October 2026, after its Supplier API live test passed.

  3. Added

    OCTO Supplier and Reseller certification

    The OCTO supplier endpoint at api.rezroute.com/octo/1 passed OCTO Supplier Certification, and the OCTO client used on the marketplace side passed OCTO Reseller Certification. Both certificates are public and are linked from the certification page. Nothing changes for an operator or a channel: no sales channel is routed through the endpoint yet, and the GetYourGuide and Viator statuses are unchanged.

Honesty

Entry shape

What each entry will carry.

Date
The day the change took effect. A release is identified by its date, in the form YYYY-MM-DD, with a letter appended if more than one release happens on the same day.
Type
Added, changed or fixed. Three words, so that a reader scanning a year of entries does not have to learn a vocabulary first.
What changed
What the change does, in the plainest terms available, and what an operator or a reviewer would notice as a result. If the answer is nothing, the entry says nothing.
Whether it affects connectivity
Marked on every entry. A change affects connectivity if it alters what a channel receives, how a product is identified, or how a call is authenticated.
Notice given
For a change affecting connectivity, the date notice was given and the date the change took effect, so the notice period is visible rather than asserted.

Versioning

What is versioned, and what is not.

There is no public RezRoute API, so there is no public version number for anyone to pin, and no deprecation cycle to run for third party clients. The versions that matter belong to the specifications implemented: the GetYourGuide Supplier API, and the Viator API versions listed on the integration reference. When a channel revises its own specification, the work to follow it appears here as an ordinary entry.

Releases are identified by date rather than by a version number, because a date is the thing an operator or a reviewer actually needs in order to line a change up against something they observed.

Notice

What is announced before it happens.

A change affects connectivity if it alters what a channel receives, how a product is identified, or how a call is authenticated. Those changes are announced before they take effect, never after.

  • GetYourGuide: at least 30 days. The Supplier API specification requires at least 30 days notice of any change affecting connectivity, and that is met as written rather than interpreted.

Notice appears on this page on the day it is given, carrying both the date of the notice and the date the change takes effect. If a change has to be made without notice, because leaving it unmade would break bookings, the entry says so and says why.