Use Repull alongside a PMS

There are two ways to use Repull. As the channel manager, it runs the host's listings, calendar and prices on every channel. Alongside the PMS or channel manager the host already has, it adds guest messaging, reservations and reviews on Airbnb, Booking.com and Vrbo — and that PMS keeps its own connection, untouched.

Why this matters

Many products need a host's guest messages, bookings and reviews without taking over their listings: a unified inbox, an AI guest assistant, a review tool, an upsell or check-in app. They work next to the host's PMS or channel manager, not instead of it. Repull connects alongside that PMS, so your product works for hosts who keep their current setup — you never ask them to switch.

What does not change for the host

Their PMS or channel manager stays connected to each channel. Nothing is disconnected or replaced.
Listings, rates, availability and content stay with the PMS. Repull does not write them in this mode.
Bookings keep arriving in the PMS exactly as before. Repull reads the same bookings; it does not take them over.
The host can remove Repull at any time, and the PMS carries on as if it was never there.

Channel by channel

Channel	Connect with	Repull reads	Repull writes	Stays with the PMS
Airbnb	OAuth with `accessType: "messaging"`	Reservations, conversations, listings	Guest messages	Listings, calendar, prices, booking settings
Booking.com	Extranet login	Reservations, guest messages, reviews	Guest messages, review replies	Rooms, rates, availability, content
Vrbo	Host sign-in with `accessType: "messaging"`	Reservations, inquiries, guest messages, reviews	Guest messages, inquiry pre-approvals and quotes, review replies	Calendar, prices, minimum stay, listing content

The Booking.com Extranet login and Vrbo are in beta. Channel details: Booking.com Extranet login, Vrbo, Airbnb access levels.

Connect a host

Start one Connect session and send the host to its URL. accessType: "messaging" makes the Airbnb and Vrbo connections messaging-only; the Booking.com Extranet login is always this mode. Limit the picker to the channels you want with allowedProviders.

curl -X POST https://api.repull.dev/v1/connect \
  -H 'Authorization: Bearer sk_live_...' \
  -H 'Content-Type: application/json' \
  -d '{
    "redirectUrl": "https://yourapp.com/connected",
    "accessType": "messaging",
    "allowedProviders": ["airbnb", "booking-extranet-login", "vrbo-login"]
  }'

# { "sessionId": "cs_...", "url": "https://connect.repull.dev/cs_...", "expiresAt": "..." }

Read and reply — the same calls on every channel

Once connected, the host's data comes through the same endpoints whichever channel and whichever mode:

GET /v1/reservations — bookings from every connected channel. Get reservations
GET /v1/conversations and POST /v1/conversations/{id}/messages — read threads and reply on the channel the guest wrote on. Send a message
GET /v1/reviews and POST /v1/reviews/{id}/reply — reviews and public replies. Reviews
Webhooks for new bookings, messages and reviews. Webhooks

Becoming the channel manager later

A host who starts alongside their PMS can move to Repull as the channel manager when they are ready: Airbnb and Vrbo with accessType: "full_access", Booking.com with the connectivity-partner connection. Moving a whole PMS account across is covered by Repull Migrate.

Previous← Quickstart NextNode.js →