StayBind for Developers

Connect a custom OTA, build a direct-booking storefront on the Booking API, and receive reservations over webhooks, all backed by one source-of-truth availability ledger.

StayBind is the operations backend for India homestays and short-stay rentals: one place to run properties, channels, bookings, guest comms, payments, and compliance. These docs are for builders who want to integrate with that backend, not operate it.

There are three ways to integrate, and they share one spine: the availability ledger, StayBind's single source of truth. A booking written anywhere blocks those dates everywhere, and a database-level constraint makes a double-booking physically impossible.

Connect a custom OTA

You run your own booking site or OTA. Feed its reservations into StayBind and let StayBind push availability back out, so it stays in sync with every other channel.

Build on the Booking API

Use StayBind as your headless backend. Browse live inventory, get a server-priced quote, place a booking, and collect payment, all with one org-scoped API key.

Receive events over webhooks

Reservations and lifecycle events delivered reliably, with signature verification, idempotency, and self-healing retries.

Reference

The canonical reservation model, error codes, rate limits, idempotency rules, and a glossary.

Which path is mine?

I have my own OTA / booking source

Use the partner-adapter path. You expose a small HTTP API and post reservations to a StayBind webhook; StayBind mirrors availability back to you. Start at Connect a custom OTA.

I want a booking front end on top of StayBind

Use the Booking API with an API key. StayBind owns inventory, pricing, the ledger, and payment links. Start at Booking API.

Principles you can rely on

The ledger is the source of truth. Channels (OTAs, your storefront, your own OTA) are projections of it. Nothing reads "live" from a channel to make a decision.
Idempotent everywhere. Every inbound reservation carries a stable id and is ingested exactly once. Re-deliveries are safe no-ops.
Self-healing. If a webhook is missed, a reconcile pass (every ~15 minutes) and a nightly full sync recover it. You never lose a booking to a dropped request.
Money is integer paise, INR. Dates are property-local YYYY-MM-DD, check-out exclusive. No floats, no timezone ambiguity.

Conventions in these docs

The StayBind API base URL is written as https://api.staybind.com throughout. Use the base URL for your environment. Example IDs (conn_…, unit_…) are illustrative.