Channel
GetYourGuide
GetYourGuide asks RezRoute whether seats are free, and RezRoute puts the question to the marketplace calendar that holds the product. Nothing is copied into a second calendar, so there is nothing to keep in step.
Certified by GetYourGuide on 20 October 2026 (Supplier API live test passed); first supplier connected through self-mapping on 21 October 2026. Last checked 2026-10-24.
What this connection does
When a traveller picks a date on your GetYourGuide listing, GetYourGuide asks RezRoute whether seats are free, and RezRoute puts that question to the marketplace calendar that holds the product, which answers from the seats it has at that second.
When the traveller pays, GetYourGuide sends the booking down the same route, and the seats are written into that same calendar inside the database transaction that checks they are still there.
There is no import, no nightly sync and no second calendar. That is why two channels cannot sell the same seat: the seat check and the write happen in one transaction, in the database that owns the seat, so two requests for the last place are settled there and one of them is refused.
Connecting
Two steps, one of them ours.
- 01
Ask us to enable the channel and issue your product identifiers
We enable GetYourGuide on your account and send you one product identifier for each tour you want listed. The identifiers are ours to issue, and each one ties a GetYourGuide product to a real departure in your calendar.
- 02
Select RezRoute in GetYourGuide and paste the identifier
In GetYourGuide Supplier Administration, select RezRoute from the list of systems, then paste the product identifier against the matching product. From that point GetYourGuide asks us for that product's availability, and you carry on managing the calendar where you already manage it.
Data
What syncs, and in which direction.
| What | Which way it travels | When |
|---|---|---|
| Availability and seat counts | GetYourGuide asks, the marketplace calendar answers | At the moment of the request. Nothing is cached by us. |
| Reservation, a hold on seats | GetYourGuide asks, the marketplace holds the seats | While the traveller is paying. |
| Reservation cancellation | GetYourGuide asks, the marketplace releases the seats | When payment is abandoned or fails, or when the hold expires. |
| Booking | GetYourGuide sends it, the marketplace writes it | On payment, in the transaction that rechecks the seats. |
| Booking cancellation | GetYourGuide sends it, the marketplace releases the seats | When GetYourGuide cancels the booking. |
| Availability you change in your portal | The marketplace tells us, we notify GetYourGuide | Through the availability update notification GetYourGuide hosts. |
| Descriptions, photographs and the traveller-facing price | Does not travel on this connection | Held in GetYourGuide and edited there. |
Endpoints
The six mandatory endpoints.
Availability query
Which dates and departures have seats, and how many. Answered from the marketplace calendar at the moment the question is asked.
Reservation
Holds seats while the traveller is paying, so nobody else can be sold them in the meantime.
Reservation cancellation
Releases a hold that is not going to become a booking.
Booking
Turns a hold into a booking. The seats are written into the calendar in the transaction that rechecks they are still free.
Booking cancellation
Cancels a booking and releases its seats back to the calendar.
Availability update notification
Hosted by GetYourGuide rather than by us, and called by us when your availability changes, so GetYourGuide learns about a change without waiting to ask.
Holds
The reservation hold, and why the window is long.
A reservation is a hold, not a booking. GetYourGuide reserves the seats while the traveller is paying, then either confirms them with a booking call or cancels the reservation. The specification asks for a sixty minute hold and sets fifteen minutes as the minimum it will accept.
While the hold is in place those seats are unavailable to everyone, including your own direct bookings and the other channel. That is the entire point of the hold: it is what stops the same seat being sold twice while a card is being charged.
It is also why a hold that never becomes a booking has to expire reliably. A long window costs you nothing when expiry is dependable, and costs you a full boat when it is not, which is why the expiry is handled by the marketplace that owns the seats rather than by a timer somewhere in the middle.
Targets
What the specification asks for.
Response time targets
| Call | Desired | 95th percentile | Longest |
|---|---|---|---|
| Reservation | 1 | 3 | 10 |
| Booking | 2 | 4 | 10 |
| Reservation cancellation | 1 | 2 | 4 |
| Booking cancellation | 1 | 4 | 6 |
| Availability, one day | 1 | 3 | 6 |
| Availability, thirty days or more | 5 | 10 | 15 |
Error ceilings per calendar month
| Call | Monthly error ceiling |
|---|---|
| Availability | Under 0.01 percent |
| Reservation | Under 1 percent |
| Booking | Under 0.5 percent |
| Booking cancellation | Under 0.5 percent |
Obligations
What the specification requires of us.
- A named technical contact
- The specification requires a named technical contact who answers GetYourGuide within 24 hours or on the next business day. That is an obligation to GetYourGuide, not a support commitment to you.
- Mapping information on request
- Any supplier who asks is given the mapping information for their own products within two business days. If you decide to leave, or to connect through somebody else, the identifiers that describe your products are yours to take.
- Thirty days notice of change
- At least 30 days notice of any change that affects connectivity, so an operator is never surprised by a change made on our side.
- One stable Supplier ID
- GetYourGuide identifies you by a single Supplier ID that does not change, so every product you connect sits under the same supplier record rather than a new one per tour.
Limits
Cancellations and amendments, and where they stop.
A booking cancellation from GetYourGuide releases the seats back into the same calendar, and they become sellable again to anyone, on any channel, immediately.
There is no amendment call in this specification. A change of date, of party size or of passenger mix is handled as a cancellation followed by a new booking. The original seats are released, and the new seats have to be free at that moment. If the new date is full, the change cannot be made through the channel at all.
Refund rules, cancellation deadlines and the conversation with the traveller belong to GetYourGuide. RezRoute moves the seats and nothing else.
Price
What this channel costs.
If your tours are listed with The Greek Local, connecting to GetYourGuide costs nothing: no setup fee, no monthly fee, and no charge per booking. The condition is the listing, not a trial period.
If your tours are listed with Cyprus Bucket List, connectivity costs nothing on the same terms.
GetYourGuide's own commission on the sale is a matter between you and GetYourGuide. It is not set by us and not collected by us. Full pricing.
Status
Where this connection has actually got to.
Last checked 2026-10-24
Built to the GetYourGuide Supplier API specification and certified by GetYourGuide on 20 October 2026 after its Supplier API live test. The first supplier was connected through self-mapping on 21 October 2026. We do not describe this connection as official or approved, and we do not describe ourselves as a GetYourGuide partner.
GetYourGuide certification runs in three phases. The last of them, the live test, was passed on 20 October 2026.
- 01
Initial self-testing
The integration is tested against the specification by us, using GetYourGuide's own test material.
- 02
Advanced self-testing
The harder paths are tested: expiring holds, refused reservations, cancellations, and the error payloads that arrive inside a 200 response.
- 03
Live testing with the GetYourGuide Connectivity team
GetYourGuide tests the connection with us. Certification follows this phase, not the two before it.
Ownership
Connect your tours to GetYourGuide.
GetYourGuide certified this connection on 20 October 2026, and the first supplier was connected on 21 October 2026. Tell us which tours you would connect and we will come back to you.