Glossary
The vocabulary used across these docs, in one place.
Adapter — the small, uniform connector for one provider (partner, direct, channex, ical, mock). The core depends only on the adapter interface, never on a specific provider.
ARI — Availability, Rates, and Inventory restrictions: the three kinds of data pushed out to channels. The atoms are AvailabilityUpdate, RateUpdate, and Restriction.
Availability ledger — StayBind's internal source of truth for what's free and what's booked, per unit per night. A database constraint makes a double-booking impossible to commit. Every channel is a projection of it.
Booking API — the public, API-key-authenticated surface at /public/trpc for building a booking front end on StayBind.
Canonical model — the provider-agnostic types every adapter translates to and from, so nothing provider-specific leaks into the core.
Connection — a configured link between an operator's org and one provider, identified by a connectionId. Holds a pointer (secretRef) to its credentials.
Conflict — a true cross-channel overbooking the ledger couldn't reflect. Terminal: a human is alerted to relocate or refund.
Idempotency — the guarantee that re-delivering the same event has no extra effect. Keyed on providerResId for reservations and the payment id for captures. See errors & reliability.
Merchant of record (MoR) — for guest/booking money, the operator is the merchant of record. StayBind never pools guest accommodation funds; it is not a payment aggregator.
Minor units (paise) — money is always an integer in paise, currency INR. ₹7,500.00 is 750000.
OTA Network — how aggregator-reached external OTAs are surfaced in StayBind. The aggregator itself is never named (vendor masking).
Partner adapter — the reusable adapter for connecting your own OTA: you provide a mapReservation function, the six endpoints, and credentials, not a new adapter.
providerResId / providerBookingId — the per-delivery idempotency key vs the stable booking id that revisions target. See idempotency.
Reconcile — the ~15-minute pull from a channel that catches any reservation whose webhook was missed.
Full sync — the nightly re-push of the forward availability horizon to every channel, correcting drift.
tRPC over HTTP — the Booking API's protocol: queries are GET …?input=<json>, mutations are POST with a JSON body, responses are wrapped as {"result":{"data":…}}.
Vendor masking — the rule that the aggregator behind external OTAs is never named in StayBind's product or API; it appears as the neutral network provider.