Connect Cloudbeds
Cloudbeds is your property management system (PMS). Once it’s connected, your agent can answer questions from live reservation data — who arrives today, who’s in house, when guests check out, what a room owes — and your team can post charges to a guest folio after an authorized approver approves them.
You connect it by creating a property-level API key inside Cloudbeds and pasting it into your workspace with your Property ID and currency.
You need: API access enabled for your Cloudbeds property and a login allowed to manage its API credentials. Check this before starting; creating a key cannot enable API access for an account that does not have it.
Step 1 — Create an API key in Cloudbeds
Follow Cloudbeds’ official API-key quickstart:
- In Cloudbeds, open Account → Apps & Marketplace → API Credentials.
- Choose + New Credentials, name the integration Tangle, and select a suitable category.
- For this API-key flow, a working OAuth redirect is unnecessary. If the
form requires a Redirect URI, Cloudbeds permits
https://localhost. Leave Enable for entire organization off for this property-only setup. - Save, then close the Client ID / Shared Secret dialog; those values are not the API key to paste into Tangle.
- In the saved credentials row, find the API Key column and choose Create. Select only the following scopes for this connector:
| Permission | What the provider key permits |
|---|---|
read:reservation | Read reservations, arrivals, departures, and balances |
read:room | Read room types and availability |
read:guest | Read guest records, including fields Tangle filters out |
read:housekeeping | Read each room’s cleaning status |
write:housekeeping | Update housekeeping status |
read:rate | Read rate plans and prices |
write:item | Post items to a guest folio |
- Create the key and complete Cloudbeds’ sign-in and scope approval. Copy the secret when shown; it cannot be displayed again.
These scopes give the key access at Cloudbeds. Tangle’s narrower behavior, including approval for folio posting, is described below.
Step 2 — Add the key to your workspace
- Open your Hospitality workspace and sign in as the owner or a manager.
- Open Integrations → Business integrations and choose Cloudbeds.
- Paste the API key, then enter:
- Property ID — the number Cloudbeds uses for your property.
- Currency — the 3-letter currency you bill in, like
USDorCRC.
- Connect. Hospitality also attempts to register this property for business data. If the connected row still offers Use for business data, select it, enter the same Property ID and currency, and confirm that action.
Where to find your Property ID
Your Property ID is a number only (for example 123456). Find it in the web
address of your Cloudbeds dashboard, as described in
Cloudbeds’ Property ID guidance.
If you need help reading it, crop a screenshot to just that part of the
address and redact any keys, tokens, guest details, or other private data
before sharing it. Never send an API-key screenshot.
Step 3 — Confirm it’s working
Check the Cloudbeds row in Integrations for an active connection and confirmation that business data uses that connection. Then ask in an appropriate staff chat:
“Who arrives today?” · “Who’s still in house?” · “What does room 12 owe?”
Compare the answer with Cloudbeds. A connected key alone does not prove that business-data registration or the latest sync has succeeded.
What your agent can and cannot do
Can do automatically: read reservations, arrivals, departures, in-house guests, guest contact details, housekeeping status, rate plans, and room availability — and update a room’s cleaning status when housekeeping reports through the agent.
Needs an authorized approver first: posting a charge through Hospitality’s folio workflow. Operations, operations lead, owner, manager, and finance roles can approve these charges. Posting requires recorded approval and live mode, with a receipt you can audit. The Cloudbeds key itself is not approval-gated.
Connector limits: Tangle’s Cloudbeds connector does not offer reservation
creation, modification, or cancellation, payment links, or payment-card data.
It filters guest identity-document fields out of its responses. This is
an application filter, not a restriction on the key: Cloudbeds’
read:guest response can include document type and number. Protect the key
as a credential capable of reading those fields directly at Cloudbeds.
If something goes wrong
| What you see | What it means | Fix |
|---|---|---|
| Connection shows Reconnect required | Cloudbeds rejected the key; it may be mistyped or replaced | Create a fresh key and reconnect in Integrations |
| Arrivals questions have no reservation data | Registration or sync has not completed, or the Property ID is wrong | Check the business-data registration and Property ID, then retry after sync |
| Housekeeping updates do not work | The key may lack write:housekeeping | Replace the key with one containing the required scopes, then reconnect |
| Folio posting is unavailable | The key may lack write:item | Replace the key with the required scopes and check the folio approval workflow |
Cloudbeds does not let you add scopes to an existing key. In API Credentials, delete the old key and create its replacement with the correct scopes, then update the Tangle connection. The old key stops working when deleted or regenerated, so plan for an interruption.
Still stuck? Share the connection row’s error text, with any private data removed. Do not share the key.
Security notes
- Tangle stores the key encrypted and does not display it again in the workspace.
- Tangle’s connector supplies your configured Property ID on requests. Keep Enable for entire organization off: a broader provider key may grant access beyond the property you configured in Tangle.
- Disconnect in Integrations to stop using the connection in this workspace. Delete the key in Cloudbeds to revoke the credential itself.