Get Mappings (via GetYourGuide's Supplier Portal GraphQL API) – when you open the connection or click Refresh Mapping, Ventrata signs in to your GetYourGuide account as the Operations user you added in Step 2, and reads all your GetYourGuide products and options, with their current status and connectivity settings. GetYourGuide doesn't publish documentation for this API; the link shows the equivalent self-service mapping concept in Ventrata's OCTO API.

Update Mappings (via GetYourGuide's Supplier Portal GraphQL API) – when you press Update Connection Mapping, Ventrata opens the corresponding product in your GetYourGuide account. It checks basic settings (such as ticket categories), clears existing availability, pricing and promotions, and writes the mapping into the option's connectivity settings. It also turns add-ons off for the option, and syncs your deals for that product straight away (see Promotions Sync).

Product Details (GET /1/products/{productId}) – when an External Product ID is entered for the first product you map, GetYourGuide asks Ventrata for its basic details, including your Ventrata API Supplier ID (= Connection ID/Key).

Products List (GET /1/suppliers/{supplierId}/products/) – using this ID, GetYourGuide pulls the list of products available on the connection, with their External Product IDs, and shows them in a dropdown to make mapping other products easier. Ventrata builds the list with OCTO Get Products (GET /products), so it contains only products enabled on the connection.

Pricing Categories (GET /1/products/{productId}/pricing-categories/) – GetYourGuide imports your product's units as its pricing categories. Ventrata reads them with OCTO Get Product (GET /products/{productId}).

Availability Query (GET /1/get-availabilities/) – GetYourGuide checks that there are at least 2 available time slots or days in the next 365 days, that the pricing categories (units) returned match those configured or imported on GetYourGuide, and that the prices are valid (for example, no currency mismatch).

Reservation (POST /1/reserve/) – GetYourGuide places a few test reservations (pending bookings), usually for the minimum and maximum allowed number of participants for each pricing category (unit type).

Reservation Cancellation (POST /1/cancel-reservation/) – GetYourGuide then cancels (releases) these test reservations.

Mapping calls happen only when someone opens or edits a connection, so they come in short bursts, not on a schedule.

Ventrata signs in to your GetYourGuide account (including GetYourGuide's two-step sign-in) each time it reads or saves your mappings.

GetYourGuide calls Product Details, Products List and Pricing Categories only while someone maps in its Supplier Portal.

Availability Query (GET /1/get-availabilities/, GetYourGuide → Ventrata) – GetYourGuide asks for a product and a date range. Ventrata answers with each available day or time slot, its remaining vacancies, its booking cut-off time and its prices, and GetYourGuide caches (stores) this in its system. Behind the scenes, the adapter looks up your mapping and calls OCTO Availability Check (POST /availability). GetYourGuide resyncs at a predefined frequency, which may vary based on many factors:

Notify Availability Update (POST /1/notify-availability-update, Ventrata → GetYourGuide) – when your availability changes because of new bookings in Ventrata, or date/time-specific changes (not bulk changes), Ventrata sends GetYourGuide the updated vacancies (and prices) for that time slot. Ventrata pushes straight away for time slots starting in the next 90 days that have 10 or fewer places left, including sold-out slots. Other changes reach GetYourGuide at its next scheduled sync.

Reservation (POST /1/reserve/, GetYourGuide → Ventrata) – when a customer adds your product to their cart on GetYourGuide, Ventrata checks again whether enough capacity remains, and rejects the reservation if not. So GetYourGuide can't overbook a slot, even if its cached availability is slightly out of date.

Availability Query: around the clock and fairly steady, with mild daytime peaks. On average, each mapped product is checked every few minutes.

About half of the requests look at dates within the next month. The rest reach further out, up to almost a year ahead.

Most requests ask about a single day; longer requests usually cover about a week.

Requested dates include a time-zone offset, so your product's timezone matters.

Notify Availability Update: pushed around the clock, within moments of the change that triggered it. Pushes come in bursts that follow booking activity and your own changes.

Pricing Categories (GET /1/products/{productId}/pricing-categories/, GetYourGuide → Ventrata) – during mapping, GetYourGuide pulls details about your product's units and updates (imports) them as its pricing categories.

Availability Query (GET /1/get-availabilities/, GetYourGuide → Ventrata) – GetYourGuide regularly calls Ventrata to resync the retail price for each ticket category, and caches it, on the same schedule as availability. The prices come from GetYourGuide's reseller pricing in Ventrata, through the OCTO Availability Check.

Notify Availability Update (POST /1/notify-availability-update, Ventrata → GetYourGuide) – when your availability changes because of new bookings in Ventrata, fares, or date/time-specific changes (not bulk changes), Ventrata sends updated retail prices to GetYourGuide.

Booking (POST /1/book/, GetYourGuide → Ventrata) – each booking carries the retail price GetYourGuide used.

Booking Size Fares – Ventrata and GetYourGuide calculate multi-unit tier structures differently, so only one mapped unit per product can use dynamic tiered pricing. Any additional fares are still allowed and work, but stay on static pricing. See an example where the Adult unit has tiered pricing enabled, while the Child and Infant units stay static:

There's no separate pricing call: prices travel with every availability answer and every push.

GetYourGuide calls Pricing Categories only while a product is being mapped.

List Deals (GET /1/deals), Delete a deal (DELETE /1/deals/{dealId}) and Create a Deal (POST /1/deals), Ventrata → GetYourGuide – for products you map from the Ventrata Dashboard (not the GetYourGuide portal), Ventrata reads your GetYourGuide special offers and checks that they match the public promotions allowed for your GetYourGuide reseller. It does this every 60 minutes. If anything doesn't match, Ventrata deletes all the special offers and recreates them to match the Ventrata Dashboard. GetYourGuide has no call to edit a deal, so every change is a delete plus a new deal.

When you save a mapping in the Ventrata Dashboard, Ventrata also syncs the deals for that product straight away.

Only basic public promotions applicable to all units with pro-rata configurations are currently supported by GetYourGuide. Other promotions aren't synced.

The deals check runs around the clock, in hourly cycles, and right after mapping changes.

Deletes and re-creates are common, because any difference rebuilds the product's deals.

Starts at

Ends at

Days Before

Notice Days

Redeemable Day

All four calls arrive around the clock, as customers shop, with daytime peaks.

There are more holds than bookings. That's normal: GetYourGuide releases almost every hold that doesn't become a booking straight away, instead of leaving it to expire.

Every booking change shows up in Ventrata as a new booking plus a cancelled one under the same reference.

If a booking call fails or times out, GetYourGuide retries it up to 10 times, every 10 minutes (see GetYourGuide's booking retries), so a booking can occasionally arrive a little after the customer paid.

Ticket Redemption by Booking Reference (POST /1/redeem-booking, Ventrata → GetYourGuide) – as soon as any of the tickets in a booking are redeemed (even if the booking is only part-redeemed), Ventrata sends a booking redemption notification to GetYourGuide. This can help prevent cancellations and refunds for redeemed bookings. However, GetYourGuide is currently known to cancel bookings regardless of the notification received.

Ventrata reports redemptions per booking. GetYourGuide's per-ticket redemption call isn't used.

Ventrata checks each update to a GetYourGuide booking and sends a notification only when the update includes a redemption.

Notifications follow your scanning: they go out around the clock, but mostly during the day, when guests arrive.

Create a list of pickup locations for each of your products/options in the GetYourGuide Supplier Portal. GetYourGuide can't currently pull them from Ventrata, so you manage them manually in their portal.

Booking (POST /1/book/, GetYourGuide → Ventrata) – GetYourGuide sends Ventrata the pickup location (the traveler's hotel) with the booking confirmation request, if this applies to your product. Using the Google Maps Places API, Ventrata matches it to the closest pickup point you offer, and also saves the exact location in the Hotel field on the booking.

Pickup details arrive only with the Booking call. GetYourGuide never asks Ventrata for your pickup points.

Mapping in the GetYourGuide portal: when you set up or map a product in the GetYourGuide portal, set the Allow Add-ons option to No. Setting it to Yes makes GetYourGuide request add-on data from the API (Fetch Addons, GET /1/products/{productId}/addons/), which Ventrata rejects, leading to connection failures.

Mapping in the Ventrata Dashboard: products mapped directly from the Ventrata Dashboard automatically have add-ons disabled during setup.