Get Products (GET /products) – when Destination Italia sets up your connection, and whenever it refreshes its listings, it reads every product enabled on the connection, with its options and units (ticket types such as Adult or Child).

Get Product (GET /products/{productId}) – Destination Italia re-reads a single product to pick up changes to its options, units, booking cutoffs and settings.

Mapping on Destination Italia's side – Destination Italia links each Ventrata option and unit to its own listing and ticket types. Your Destination Italia account manager does this for you, or you do it in Destination Italia's own portal if Destination Italia offers one. You only share the connection's API key.

Destination Italia reads your full product list every few days.

It re-reads each product about every 2 hours.

octo/content capability – when Destination Italia adds it to the Octo-Capabilities header, Get Products (GET /products) and Get Product (GET /products/{productId}) also return your product content, such as descriptions, highlights, inclusions and images.

Content changes in Ventrata reach Destination Italia on its next product refresh.

Destination Italia requests octo/content.

Availability Check (POST /availability) – Destination Italia sends a product, an option and a date or date range. Ventrata answers with each bookable day or time slot, its status (AVAILABLE, LIMITED, SOLD_OUT, CLOSED or FREESALE), the remaining vacancies, the booking cutoff and an availabilityId, which Destination Italia needs to book that slot.

Availability Calendar (POST /availability/calendar) – returns one summary per day instead of every time slot, typically to show which dates are open in a date picker.

Check at booking – when a customer books, Ventrata checks capacity again before it creates the booking, so Destination Italia can't overbook a slot that has just sold out, even if its stored availability is slightly out of date.

Availability Check: Destination Italia checks your products throughout the day, usually starting today and covering about a year per request, looks up to about a year ahead and re-checks the same product and dates about every 10 hours.

Availability Calendar: Destination Italia checks your products throughout the day, usually starting 13 days ahead and covering about 4 months per request, looks up to about a year ahead and re-checks the same product and dates about every 7 hours.

Checks are busiest between 11:00 and 17:00 UTC, which suggests most checks are live, as customers browse Destination Italia.

octo/pricing capability – Destination Italia asks for prices by adding octo/pricing to the Octo-Capabilities header of its requests. Without it, Ventrata sends availability with no prices at all.

Availability Check (POST /availability) – with pricing on, each day or time slot comes back with your price per unit (ticket type): the retail price the customer pays and the net price you invoice Destination Italia, both from the reseller's pricing in Ventrata (retail and wholesale/commission).

Group prices – when Destination Italia also sends how many people of each unit type are booking, Ventrata prices that exact group. This matters for Booking Size fares and other group pricing.

Booking Reservation (POST /bookings) and Booking Confirmation (POST /bookings/{uuid}/confirm) – the booking comes back with its final retail and net price, so the booking in Ventrata always records the price it was sold at.

Destination Italia requests octo/pricing on all of its availability checks, so it sells at your Ventrata prices.

Destination Italia doesn't send the number of people per unit type, so prices come back per person, and group pricing such as Booking Size fares may not show correctly on Destination Italia.

Destination Italia doesn't set a hold time, so the default hold time applies.

A typical Destination Italia booking is for about 2 people.

Destination Italia also checks the bookings it has made, with Get Booking (GET /bookings/{uuid}) about every 8 hours, for example to reconcile its records.