Cloudbeds API

The Cloudbeds API is how you extend the platform instead of replacing pieces of it. It gives you open, two-way access to the same data model that runs Cloudbeds itself: one guest profile, one reservation, one ledger. Our newest services — Accounting, Guest Profile, Group Profile, and Attribute Tagging — are built REST-first, and the full platform is documented over HTTP with GraphQL support for flexible querying.

Anything that maps to a real workflow: a custom booking flow for your own site, app, or kiosk; POS and back-office sync so charges post automatically; guest-journey automation triggered off real-time reservation events; rate pushes from your RMS; or a build that works across your whole portfolio with one credential set. If you’re building for the industry rather than just your own properties, you can also package it and list it in the Cloudbeds Marketplace, in front of 20,000+ properties in 150+ countries.

100% of endpoints are available across six areas: Operations & Reservations, Payments, Distribution, Guest, Webhooks & Events, and Identity & Access. Because there’s one data model behind all of it, you’re always reading and writing the same guest, reservation, and ledger records the rest of the platform uses — not a separate copy that has to be reconciled later

Yes. Webhooks let your integration react the moment something changes in Cloudbeds — a new reservation, a rate update, a guest check-in — instead of polling or waiting on a batch sync. Combined with GraphQL, you can also query exactly the data you need in a single call rather than assembling it from several endpoints.

Yes — that’s a core part of the design, not a workaround. The group-level API gives you one set of credentials across one, several, or all properties in a portfolio, so IT and multi-property teams can standardize access and governance instead of managing separate keys per property.

Six steps: find the right API for your use case in the reference and guides, import the public Postman collection or spin up sandbox credentials at api.cloudbeds-stage.com to start testing immediately, authenticate via OAuth 2.0, request scoped production credentials, go through certification if you’re building for other hoteliers or the marketplace, and go live — either to your own properties or out to the full Cloudbeds network.

Yes. api.cloudbeds-stage.com is a full staging environment that mirrors production, so you can build and test without touching a live property. A public Postman collection is also available if you’d rather start making calls than start reading reference docs.

Yes — limits are published per credential set, and API responses include headers showing your remaining quota, so you can build retry and backoff logic around known limits rather than guesswork.