Reference · built on requestConnectorHospitality & property systems

Cloudbeds

Reservations, guests, rooms, rates, and housekeeping from a Cloudbeds property, with webhooks per object and action.

Request accessPricing ↗

About

Cloudbeds is a property management system with a built-in channel manager and booking engine. Its PMS API is served at api.cloudbeds.com/api/v1.3 with operations named as verbs, such as getReservations, getGuest, getRooms, getRatePlans, and postHousekeepingStatus. Webhooks are subscribed per object and action, for example reservation/status_changed or housekeeping/room_condition_changed. Two further APIs, Data Insights and Accounting, cover reporting datasets and posted transactions.

Through Fibric, an operator reads the reservation or room behind each webhook and proposes a status change, a housekeeping update, or a reservation note for your approval, leaving a receipt of what changed and how to undo it.

This is a reference listing. It documents what Fibric would read from Cloudbeds and what it could propose, based on the vendor's published interfaces. Fibric builds it under a managed deployment when you request it; selecting it here installs nothing.

Inputs

  • Reservations through getReservations, filtered by status (not_confirmed, confirmed, canceled, checked_in, checked_out, no_show), check-in dates, or modification date
  • Reservation webhooks: reservation/created, reservation/status_changed, reservation/dates_changed, reservation/accommodation_changed, reservation/notes_changed
  • Guests through getGuest, getGuestList, and getGuestsModified, plus guest/created, guest/assigned, and guest/details_changed events
  • Rooms and room types through getRooms, getRoomTypes, and getAvailableRoomTypes; housekeeping through getHousekeepingStatus and getHousekeepers
  • Housekeeping events housekeeping/room_condition_changed and housekeeping/housekeeping_room_occupancy_status_changed; night_audit/completed
  • Rates and rate plans through getRate and getRatePlans; taxes and fees; the property overview through getDashboard
  • Posted and pending transactions through the Accounting API search endpoints; reporting datasets through the Data Insights API

Proposed actions

  • Target capability: propose a reservation status, estimated arrival time, or custom field change with putReservation
  • Target capability: propose a room condition of clean, dirty, or inspected, with doNotDisturb and roomComments, through postHousekeepingStatus
  • Target capability: propose a reservation note with postReservationNote, or a change to one with putReservationNote
  • Target capability: propose a new reservation with postReservation, or a rate change with patchRate (queued, up to 30 intervals per call)

Proposed actions are target capabilities. Every action runs propose-first and needs a validated deployment and the appropriate permissions.

What you can build

  • Ready the room for an early arrival

    Read today's confirmed arrivals with estimated arrival times, compare with getHousekeepingStatus, and propose a cleaning order or an inspected status for the housekeeper to approve.

    With Arrival Prep, Room Ready

  • Flag a no-show before night audit

    After check-in time passes with no checked_in status, propose the no_show status on putReservation and a note explaining the timing, before night_audit/completed.

    With Walk Risk, No-Show Response

  • Respect do-not-disturb

    When a room's doNotDisturb flag is set, propose skipping the service and a follow-up time, and clear the flag afterwards through postHousekeepingStatus.

    With DND Check

  • Keep guest details current at the desk

    Subscribe to guest/details_changed and reservation/notes_changed, read the guest, and propose a reservation note the front desk sees at check-in.

    With VIP Recognition, Pre-Arrival Fix

Requirements

  • A Cloudbeds property, or an organization with the key enabled for several properties, and a user who can approve the selected scopes
  • Scopes matching the calls made: read:reservation, read:guest, read:room, read:housekeeping, read:rate, plus write:reservation or write:housekeeping for proposals
  • An HTTPS endpoint that returns a 2XX response to webhook deliveries
  • For rate changes, non-derived rates; a request to update a derived rate returns an error
Authentication
A Cloudbeds API key (prefixed cbat_) created under Account > Apps & Marketplace > API Credentials with the scopes you select, sent as a bearer token or in the x-api-key header; OAuth 2.0 with the authorization code grant remains an alternative.

Limits

  • An API key stops working if unused for 30 days; OAuth access tokens last 8 hours (28800 seconds)
  • Webhooks are one subscription per object and action, and a failed delivery is retried every minute up to five attempts
  • getReservations returns at most 100 records per page
  • getTransactions and related endpoints are deprecated in favour of the Accounting API; Cloudbeds publishes no numeric request limit

Access and pricing

Reference listing. Fibric builds the connector under a managed deployment when you request it. Your quote covers the build, capabilities, usage, and support.

Request Cloudbeds ↗

Questions and answers

How does a property give Fibric access to Cloudbeds?
A property user creates API credentials under Account > Apps & Marketplace, creates an API key on that entry, ticks the scopes it should carry, and approves them with a Cloudbeds login. The key begins with cbat_, is shown once, and can cover one property or an organization.
Which Cloudbeds events can the connector subscribe to?
Cloudbeds webhooks are per object and action. Reservation actions include created, status_changed, dates_changed, accommodation_changed, notes_changed, and deleted. Guest, housekeeping, night_audit, accounting, doorLockKey, roomblock, and allotmentBlock objects have their own actions. Each subscription names one action; Cloudbeds does not support subscribing to all actions on an object.
What happens if the webhook endpoint is down?
Cloudbeds calls the endpoint again after a one-minute delay and repeats, one minute apart, until a request succeeds or five attempts have been made. Any 2XX response counts as success.
Ask about Cloudbeds

Ask about the capabilities and requirements in this listing.

For project-specific requirements, contact Fibric.

This connector listing is developed, published, and supported by Fibric. It describes integration with Cloudbeds through published interfaces. Third-party names and logos identify the systems an integration connects to; they are the property of their respective owners, who are not affiliated with Fibric and do not sponsor or endorse this listing. Trademark policy