> For the complete documentation index, see [llms.txt](https://docs.coupler.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.coupler.io/sources/category/other/cloudbeds/data-overview.md).

# 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

{% tabs %}
{% tab title="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
  {% endtab %}

{% tab title="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
  {% endtab %}

{% tab title="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
  {% endtab %}

{% tab title="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
  {% endtab %}
  {% endtabs %}

## 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)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.coupler.io/sources/category/other/cloudbeds/data-overview.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.