Workspace: Luxury Portfolio · Executive Suite

Global line: +1 (800) AIR-BELLStripe:Connected
Home

Setup

Connect your booking site or channel manager

A guided walkthrough for pointing your existing systems at Airbel — written in plain English first, with the technical detail underneath each step.

Time to first live call

Under an hour

Systems supported

PMS, channel manager, direct site

Guest data

Stays in your backend

  1. 1

    Pick the system that owns your calendar

    Whatever your team already logs into every morning — Guesty, Hostaway, Lodgify or a channel manager sitting on top of Airbnb and Vrbo. Airbel sits on top of it and never asks you to move.

    Open Integrations and find your provider card. Each one has its own inbound webhook URL and token — nothing is written back into your PMS, Airbel only listens.

  2. 2

    Point your PMS webhooks at that URL

    Your listings, their wifi passwords, parking notes and checkout times, plus every reservation, flow into Airbel automatically as they change.

    In your PMS webhook settings, add POST https://your-site/api/public/pms/guesty (or /hostaway, /lodgify, /generic) with the header x-airbel-pms-token from that provider's card. Listing and reservation events are matched on the PMS's own IDs, so repeats update instead of duplicating, and cancellations clear scheduled turnovers.

  3. 3

    Let Airbel read the calendar during a call

    When a guest asks for one more night, the concierge checks that calendar live, on the call, before it says yes.

    Your PMS or automation tool calls POST /api/public/workflows/booking-check with the guest, property and date range. Airbel replies with availability plus a hold on the reservation when create_hold is true.

  4. 4

    Send payment events back to Airbel

    As soon as the card clears, the guest gets a door code by text — nobody has to remember to send it.

    In Stripe → Developers → Webhooks, add an endpoint for payment_intent.succeeded pointing at /api/public/workflows/payment-success.

  5. 5

    Point maintenance issues at your vendors

    If a guest reports a leak, a ticket opens and your local vendor gets a text with a one-time entry code.

    The voice agent posts to /api/public/workflows/maintenance-dispatch with the issue description and property. Vendor numbers are configured per property in Integrations.

Copy & paste

What your automation tool sends

Availability / extension check (JSON)
POST https://airbel.app/api/public/workflows/booking-check
Content-Type: application/json

{
  "guest_name": "Céline Marchand",
  "guest_phone": "+33 6 12 34 56 78",
  "property_name": "Villa Étoile · Aspen",
  "check_in": "2026-08-14T16:00:00Z",
  "check_out": "2026-08-17T11:00:00Z",
  "create_hold": true
}

Live endpoint URLs and one-click test triggers for all three paths live on the Workflows page.

Not sure which route fits your setup?

If your calendar lives in a PMS, start with the first track. If you take bookings on your own site, start with the second — most portfolios end up using both.