Cloudbeds

Cloudbeds is an all-in-one hospitality management platform used by hotels, hostels, and vacation rentals to manage reservations, guests, rooms, and payments. Connecting Cloudbeds to Coupler.io lets you pull your property data into any destination for reporting, analysis, or AI-powered workflows.

Why connect Cloudbeds to Coupler.io?

• Centralize your property data — combine reservations, transactions, guests, and room inventory in one place

• Automate reporting — send live data to Google Sheets, Looker Studio, BigQuery, or Excel without manual exports

• Unlock AI insights — pipe your hospitality data into ChatGPT, Claude, Gemini, or Perplexity to analyze trends and answer questions

• Combine multiple entities — use Join or Append transformations to merge reservations with guest profiles or transaction records

Prerequisites

• An active Cloudbeds account

• A Cloudbeds API key (generated from your Cloudbeds developer settings)

• Access to the property or properties you want to export

Quick start

Start with the Reservations entity — it's the most commonly used and connects naturally with Guests and Transactions for a full booking picture.

How to connect

1

Create a new data flow in Coupler.io. Log in to your Coupler.io account and click Add data flow. Search for and select Cloudbeds as your source.

2

Enter your Cloudbeds API key. In the source settings, paste your Cloudbeds API key into the API key field. You can find this in your Cloudbeds account under Settings > API > Generate API key.

3

Select an entity. Choose which data you want to import — Guests, Hotels, Rooms, Reservations, Transactions, or Packages.

4

Choose a destination. Select where you want your data to land — Google Sheets, Excel, BigQuery, Looker Studio, or an AI destination like ChatGPT, Claude, or Gemini.

5

Run your data flow. Click Run to execute the data flow manually. Once it completes successfully, your Cloudbeds data will appear in your chosen destination.

Cloudbeds data overview

Cloudbeds exposes six core entities through Coupler.io, covering the full operational picture of a hospitality property — from guest profiles and room inventory to reservations, payments, and service packages.

Entities overview

Entity	What it contains
Guests	Contact details, guest history, preferences
Hotels	Property name, location, configuration, settings
Rooms	Room types, descriptions, bed types, rates, availability
Reservations	Check-in/out dates, status, source, room assignment, guest link
Transactions	Payment amounts, types, dates, reservation links
Packages	Package names, pricing, inclusions, availability

Available fields

Guests

Field	Description
Guest ID	Unique identifier for the guest
First name / Last name	Guest's full name
Email	Contact email address
Phone	Contact phone number
Country	Guest's country of origin
Gender	Gender on file
Created date	When the guest profile was created

Hotels

Field	Description
Hotel ID	Unique property identifier
Property name	Name of the hotel or property
Address	Full property address
City / State / Country	Location details
Currency	Default billing currency
Time zone	Property time zone

Rooms

Field	Description
Room ID	Unique room identifier
Room name	Room label or number
Room type	Category (e.g., double, suite)
Max occupancy	Maximum number of guests
Description	Room details and amenities
Status	Active or inactive

Reservations

Field	Description
Reservation ID	Unique booking identifier
Guest ID	Linked guest profile
Check-in date	Scheduled arrival date
Check-out date	Scheduled departure date
Status	Confirmed, cancelled, checked-in, checked-out
Room ID	Assigned room
Source	Booking origin (direct, OTA, etc.)
Total amount	Total booking value
Adults / Children	Guest count breakdown

Transactions

Field	Description
Transaction ID	Unique payment identifier
Reservation ID	Linked reservation
Amount	Payment amount
Transaction type	Charge, payment, refund
Transaction date	Date the transaction occurred
Description	Line item description

Packages

Field	Description
Package ID	Unique package identifier
Package name	Display name
Price	Package cost
Description	What's included
Availability	Which room types it applies to

Common field combinations

• Reservations + Guests — Join on Guest ID to build a full booking report with guest contact details

• Reservations + Transactions — Join on Reservation ID to reconcile booking revenue against actual payments

• Rooms + Reservations — Join on Room ID to analyze occupancy rates by room type

• Transactions + Packages — Combine to track package revenue separately from room revenue

Use cases by role

Revenue managers

• Pull Reservations and Transactions to track RevPAR, ADR, and occupancy trends over time

• Use Aggregate transformation to sum revenue by booking source or room type

• Send data to Looker Studio or BigQuery for dashboarding

Front office teams

• Export Reservations with check-in/out dates to Google Sheets for daily arrival/departure lists

• Join Guests to Reservations for a complete guest profile at check-in

• Use AI destinations like ChatGPT or Claude to answer natural language questions about upcoming bookings

Finance teams

• Pull Transactions to reconcile payments and identify outstanding balances

• Append transaction data from multiple properties using the Append transformation

• Export to Excel or BigQuery for accounting workflows

Operations teams

• Monitor room status and inventory using the Rooms entity

• Combine Rooms with Reservations to spot availability gaps

• Track package uptake by joining Packages with Reservations

Platform-specific notes

• Cloudbeds uses a property-scoped API — your API key only returns data for the property it was generated under

• If you manage multiple properties, you'll need a separate API key per property and can use the Append transformation to combine data across properties in a single data flow

• Reservation statuses may vary slightly depending on your Cloudbeds plan and configuration

• Date fields are returned in ISO 8601 format (YYYY-MM-DD)

Cloudbeds common issues

Connection issues

My API key is not being accepted

Double-check that you copied the full API key from Cloudbeds without any leading or trailing spaces. API keys are generated under Settings > API in your Cloudbeds account — make sure you're using a key that has been fully activated, not a placeholder or partial key.

If the key was recently regenerated, the old key will no longer work. Update the API key field in your Coupler.io data flow source settings.

The data flow fails immediately after connecting

This usually means the API key doesn't have sufficient permissions for the entity you selected. Check that the key was generated with read access to the relevant data (guests, reservations, etc.) in Cloudbeds. If you're on a restricted Cloudbeds plan, some endpoints may not be available.

Missing data

Only one property's data is showing up

Cloudbeds API keys are scoped to a single property. If you manage multiple properties and want data from all of them, you need to generate a separate API key for each property, create separate data flows or sources, and use the Append transformation to combine them.

Some reservations or guests are missing

Cloudbeds may paginate large result sets, and historical records may have limits depending on your plan tier. Check whether the missing records are older than your plan's data retention window. If you're expecting very recent records, allow a few minutes after they're created in Cloudbeds before re-running the data flow.

The Packages entity returns no data

Packages are only returned if at least one package has been configured and made active in your Cloudbeds account. If you haven't set up any packages, the entity will return an empty result — this is expected behavior.

Permission errors

I see a 403 Forbidden error

This means the API key used does not have permission to access the requested resource. Log in to Cloudbeds, navigate to Settings > API, and verify that the key has the necessary read permissions. If permissions were recently changed, regenerate the key.

If your Cloudbeds account is on a lower-tier plan, some entities (such as advanced transaction data) may be restricted at the plan level, not the key level.

Data discrepancies

Revenue figures in Coupler.io don't match Cloudbeds reports

Cloudbeds' built-in reports may apply additional filters (e.g., only confirmed reservations, or excluding taxes) that the raw API data does not. When building your own reports, check whether you need to filter by reservation status or transaction type to match the Cloudbeds report logic.

Check-in and check-out dates look off by one day

Date fields from the Cloudbeds API are returned in the property's local time zone. If your destination (e.g., BigQuery) interprets dates as UTC, you may see a one-day shift for properties in non-UTC time zones. Confirm the time zone of your property in Cloudbeds and account for this in your data model.

Rate limits

My data flow is failing due to rate limit errors

Cloudbeds enforces API rate limits per key. If you're running multiple data flows with the same API key simultaneously, you may hit these limits. Try staggering your data flow schedules or reducing the frequency of runs for less time-sensitive entities like Hotels or Rooms.

Cloudbeds FAQ

Where do I find my Cloudbeds API key?

Log in to your Cloudbeds account and go to Settings > API. From there you can generate a new API key. Copy the full key and paste it into the API key field in your Coupler.io data flow source settings.

Note that if you regenerate the key, your existing Coupler.io data flows will stop working until you update them with the new key.

Can I pull data from multiple Cloudbeds properties?

Yes, but you'll need a separate API key for each property since Cloudbeds API keys are property-scoped. Create a separate source in Coupler.io for each property, then use the Append transformation to merge the data into a single destination table. You can do this within a single data flow that has multiple sources.

Which entity should I start with?

Start with Reservations — it's the central entity in Cloudbeds and links to guests, rooms, transactions, and packages. Once you have reservations flowing, join the other entities to enrich your data.

Can I send Cloudbeds data to an AI tool like ChatGPT or Claude?

Yes. Coupler.io supports AI destinations including ChatGPT, Claude, Gemini, Perplexity, Cursor, and OpenClaw. You can send any Cloudbeds entity to these destinations to ask natural language questions about your bookings, guests, or revenue.

Why does my transaction data not match the revenue figures in Cloudbeds?

Cloudbeds' built-in reports apply filters (such as excluding cancellations or separating taxes) that aren't applied to the raw API data. To match report figures, filter your transaction data by type and reservation status in your destination or using Coupler.io's Aggregate transformation.

See Data Overview for a breakdown of transaction fields and Common Issues for more on data discrepancies.

How often can I refresh Cloudbeds data?

Cloudbeds enforces API rate limits. For high-frequency entities like Reservations and Transactions, refreshing every hour or every few hours is typically safe. For stable entities like Hotels and Rooms, daily or less frequent refreshes are sufficient and help you stay within rate limits.

See Best Practices for scheduling recommendations.

What happens if I regenerate my Cloudbeds API key?

Your existing Coupler.io data flows will fail because the stored key is no longer valid. Go into each affected data flow's source settings and update the API key field with the newly generated key, then run the data flow manually to confirm it works.

Can I combine Cloudbeds data with data from other sources?

Yes. Coupler.io lets you add multiple sources to a single data flow. For example, you could combine Cloudbeds reservation data with marketing data from another platform and use the Join or Append transformation to merge them before sending to your destination.