> 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/faq.md).

# FAQ

<details>

<summary>Where do I find my Cloudbeds API key?</summary>

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.

</details>

<details>

<summary>Can I pull data from multiple Cloudbeds properties?</summary>

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.

</details>

<details>

<summary>Which entity should I start with?</summary>

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.

</details>

<details>

<summary>Can I send Cloudbeds data to an AI tool like ChatGPT or Claude?</summary>

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.

</details>

<details>

<summary>Why does my transaction data not match the revenue figures in Cloudbeds?</summary>

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.

{% hint style="info" %}
See [Data Overview](/sources/category/other/cloudbeds/data-overview.md) for a breakdown of transaction fields and [Common Issues](/sources/category/other/cloudbeds/common-issues.md) for more on data discrepancies.
{% endhint %}

</details>

<details>

<summary>How often can I refresh Cloudbeds data?</summary>

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.

{% hint style="info" %}
See [Best Practices](/sources/category/other/cloudbeds/best-practices.md) for scheduling recommendations.
{% endhint %}

</details>

<details>

<summary>What happens if I regenerate my Cloudbeds API key?</summary>

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.

</details>

<details>

<summary>Can I combine Cloudbeds data with data from other sources?</summary>

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.

</details>


---

# 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/faq.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.