Build against the Sabee API.

The Sabee API is available on the Growth tier and above (see pricing), and covers the same data your reception, revenue and accounting teams see inside the product — reservations, rate plans, room types, guests, channel status and invoices. It is a plain JSON-over-HTTPS REST API authenticated with a bearer API key, with cursor-based pagination for list endpoints and a versioned base path so integrations don't break silently when the platform evolves.

Most integrations fall into one of three patterns. The first is a read-heavy sync into an external system — pulling reservations and invoices into a data warehouse or a group-level BI tool that sits outside Sabee's own Revenue Analytics module. The second is a write path — a channel, booking widget or internal tool creating and updating reservations directly through the API rather than through the Sabee dashboard. The third is event-driven — subscribing to webhooks so an external system reacts the moment a reservation is created, a guest profile is updated, or an invoice is paid, without polling the API on a schedule.

The four reference pages below cover what you need for any of these patterns. The API reference documents authentication, every endpoint, request and response shapes, pagination and versioning, with runnable curl examples for each. The webhooks page covers the full event catalogue, payload shapes, how to verify the HMAC signature on every delivery, the retry policy for failed deliveries, and the test endpoint for exercising your webhook handler before going live. The rate limits page documents the request quota for each plan tier, the rate-limit headers returned on every response, and how to handle a 429 response gracefully. The error codes page is a full reference of both standard HTTP status codes and Sabee-specific error codes, each with an example JSON response body so you can build reliable error handling rather than guessing at failure modes.

If you get stuck on something not covered here, or you're planning an integration that needs a capability the current API doesn't expose, reach out through contact — API and webhook coverage grows based on real integration requests, and Enterprise customers can commission specific endpoints against their own SLA.

A quick orientation note before you dive in: every example on these pages uses the production base URL, a placeholder API key, and realistic but fabricated reservation and guest data. None of the sample identifiers, dates or amounts correspond to a real property or a real guest — copy the shape of the request, not the values, and substitute your own API key from the dashboard once you're ready to test against your own account.