Exchange Code For Tokens (POST /v2/oauth2/authorizations) – Ventrata → Airbnb, once, when you click Connect with Airbnb and Allow. Airbnb gives Ventrata access to manage the calendar and bookings of your Airbnb listings. Airbnb's access tokens are short-lived, so Ventrata renews this access automatically in the background (Refresh Access Token, same path).

Get Activities (GET /v2/activities) and List all offerings (GET /v2/activities/{id}/offerings) – Ventrata → Airbnb, when you open the connection page. Ventrata reads your Airbnb listings and shows them on the left of the mapping table.

Set Attributes (PUT /v2/activities/{id}/attributes) – Ventrata → Airbnb, when you click Update Mapping. After reading the listing, Ventrata sends the guest types your option sells (Adult, Child, Infant), their age limits from your Ventrata units, and the minimum age.

Set Activity Availability (PUT /v2/activities/{id}/availability) – Ventrata → Airbnb, on Update Mapping. Ventrata switches on availability sync, which makes Ventrata the source of truth for the listing and turns on Airbnb's live checks before every booking.

Set Offering (PUT /v2/activities/{id}/offerings/{id}) – Ventrata → Airbnb, on Update Mapping. Ventrata stores your Ventrata connection, product and option IDs on the Airbnb offering. Airbnb sends these IDs back with every check and booking, which is how Ventrata knows which product a guest is booking.

Set Offering Availability (PUT …/offerings/{id}/availability) and Set Offering Pricing (PUT …/offerings/{id}/pricing) – Ventrata → Airbnb, on Update Mapping. Ventrata sets the listing-wide group limits, booking lead time and booking type (for example, a shared public booking), so the capacity Ventrata sends per time slot and Ventrata's live check decide what can be booked.

Set Instances (POST /v2/activities/{id}/instances) – Ventrata → Airbnb, at the end of Update Mapping. Ventrata creates your time slots on Airbnb's calendar (see Availability Sync).

Queued mapping updates – some mapping updates run as a background job with the same steps. The job reads your product through Ventrata's OCTO API with Get Product (GET /products/{productId}).

Mapping calls happen only when someone connects, opens a connection page or clicks Update Mapping.

Access renewals and queued mapping updates run in the background around the clock.

Get Instances (GET /v2/activities/{id}/instances) and Set Instances (POST /v2/activities/{id}/instances) – Ventrata → Airbnb, as soon as availability changes in Ventrata, for example after a booking on any channel, a cancellation, or a change to capacity or the schedule. Ventrata reads the time slots Airbnb has for the affected dates, compares them with Ventrata, and sends only the differences in one batch: new time slots to create, slots whose guest limit (places left) or price has changed, and slots to remove because they're no longer available.

Ventrata OCTO API – to work out each update, Ventrata's adapter reads your product and live availability through Ventrata's own OCTO API: Get Product (GET /products/{productId}) and Availability Check (POST /availability).

Background resync – Ventrata → Airbnb, around the clock. A scheduled job goes through mapped listings, compares Airbnb's time slots with Ventrata again and corrects any that have drifted, again sending only the differences. Some availability updates are also queued and sent as a background job.

Check Availability (GET /airbnb/endpoint/reservation) – Airbnb → Ventrata, live, before a guest moves into checkout. Airbnb sends the listing, the Ventrata product and option IDs stored at mapping, the start time and the number of adults, children and infants. Ventrata looks up the product with Get Product (GET /products/{productId}), checks that time slot and those guest types in real time, and answers yes or no. Airbnb expects an answer within 2 seconds. If the answer is no, or the check fails or takes too long, the guest can't book, and Airbnb removes that time slot from its calendar.

Availability pushes run around the clock, following the bookings and changes that happen in Ventrata. They cover dates from today up to about a year ahead, most of them for the next few weeks.

The background resync runs around the clock.

Check Availability arrives evenly around the clock, mostly for dates in the next four weeks. Airbnb checks much more often than guests book, so most checks don't lead to a booking.

Set Offering Pricing (PUT /v2/activities/{id}/offerings/{id}/pricing) – Ventrata → Airbnb, on Update Mapping. Ventrata sets the listing's pricing settings, for example that it's sold as a shared public booking.

Set Attributes (PUT /v2/activities/{id}/attributes) – Ventrata → Airbnb, on Update Mapping. Ventrata sends your guest types and age ranges, so Airbnb's Adult, Child and Infant match your Ventrata units.

Set Instances (POST /v2/activities/{id}/instances) – Ventrata → Airbnb, with availability updates. When a time slot's price needs updating, Ventrata sends the adult, child and infant price for that slot, so date- and time-specific prices in Ventrata reach Airbnb. Prices come from the Airbnb reseller's pricing in Ventrata.

Booking Size fares – the partner tier counts are synced when you click Update Mapping. After every fare change, update the product mapping again, and make sure the fare is enabled for sale over the Direct API.

Prices travel with the availability pushes, around the clock. Most pushes only change the places left; prices are included when a slot's price needs updating.

Listing-wide pricing settings and guest types are sent only on Update Mapping.

Bookings, changes and cancellations arrive around the clock, and each is handled as it happens.

Each new booking reaches Ventrata as a Make Reservation call and as a webhook. Ventrata matches them by the Airbnb confirmation code.

A ticket message follows each new booking.

Change checks (Update Reservation) are rare.

Tickets – Ventrata → Airbnb, right after each booking: the PDF ticket link, the wallet ticket link and, for some products, QR code images, all in the guest's Airbnb messages (see Bookings Sync). Guests show them at your entrance, and you scan and redeem them in Ventrata like any Ventrata ticket.

No redemption updates – Ventrata doesn't send Airbnb an update when a ticket is scanned or redeemed, or when a guest doesn't show up.

We see no calls that report redemptions or no-shows to Airbnb.