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

# Common Issues

## Connection issues

<details>

<summary>My API key is not being accepted</summary>

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.

</details>

<details>

<summary>The data flow fails immediately after connecting</summary>

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.

</details>

## Missing data

<details>

<summary>Only one property's data is showing up</summary>

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.

</details>

<details>

<summary>Some reservations or guests are missing</summary>

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.

</details>

<details>

<summary>The Packages entity returns no data</summary>

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.

</details>

## Permission errors

<details>

<summary>I see a 403 Forbidden error</summary>

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.

{% hint style="warning" %}
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.
{% endhint %}

</details>

## Data discrepancies

<details>

<summary>Revenue figures in Coupler.io don't match Cloudbeds reports</summary>

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.

</details>

<details>

<summary>Check-in and check-out dates look off by one day</summary>

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.

</details>

## Rate limits

<details>

<summary>My data flow is failing due to rate limit errors</summary>

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.

</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/common-issues.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.