Overview
Plug your own OTA or booking source into StayBind through the partner adapter. Reservations flow in; availability flows out; one ledger keeps you in sync with every other channel.
If you run your own booking site or OTA, you can connect it to StayBind so that:
- every reservation you take flows into StayBind's ledger (and blocks those dates on every other channel the operator syncs), and
- StayBind pushes availability back out to you whenever a booking lands anywhere else.
You do this through the partner adapter, a generic, reusable connector. You do not write an adapter from scratch. The HTTP plumbing, retries, idempotency, reconcile, and ack are already built. Connecting a new OTA is "expose a small API, post your reservations to a webhook, and hand over credentials."
How it fits together
BOOKINGS IN
Your OTA ──POST reservation──▶ StayBind webhook
│ normalize + write (idempotent)
▼
Availability ledger ──fan-out──▶ block/release those
dates on every channel
AVAILABILITY OUT
A booking lands on another channel ──▶ Availability ledger
│ the dates that changed
▼
POST /availability ──▶ Your OTA mirrors itTwo directions, two mechanisms:
| Direction | Mechanism | You build |
|---|---|---|
| Bookings in | you POST reservations to a StayBind webhook (StayBind also pulls as a backup) | the webhook calls + the GET /reservations pull endpoint |
| Availability out | StayBind POSTs availability/rate/restriction updates to your API | the POST /availability, /rates, /restrictions endpoints |
What you provide
A small HTTP API StayBind can call to mirror availability and pull reservations. Six endpoints, all under one base URL. See Expose your API.
Reservation deliveries posted to your StayBind channel webhook whenever a booking is created, changed, or cancelled. See Receive bookings.
Credentials: your API's baseUrl, an apiKey StayBind sends as a bearer token, and a webhookSecret that signs your inbound deliveries. These are stored in StayBind's secret store against your connection, never in the database. See Map reservations.
What StayBind provides
- A connection (
connectionId) that ties your credentials to the operator's org, created by the operator in the Channels screen (or provisioned with the operator API). - A
mapReservationfunction that translates your reservation payload into StayBind's canonical model. Send the default shape and it works out of the box; send your own and StayBind configures a mapper to it. - All reliability machinery: idempotent ingestion, a ~15-minute reconcile pull as a missed-webhook backup, a nightly full availability re-push, and per-account rate limiting on outbound calls.
The contract in one line
You expose six endpoints and post your reservations to one webhook. StayBind keeps your calendar in lockstep with every other channel, and guarantees no double-booking.
Start with Expose your API.