Cloudbeds access guide

How to access your Cloudbeds account

This guide walks through, step by step, how to sign in to the Cloudbeds platform, retrieve your API credentials and restore access when you are locked out. Instructions cover both the connection from Cloudpmsbed and the most common incidents property administrators run into.

Updated: June 2026 Reading time: 8 minutes Audience: Cloudbeds administrators

Note: Cloudpmsbed is an independent third-party service and is not affiliated with Cloudbeds Inc. This guide describes the general procedure based on publicly available information. Menu labels and the exact navigation path may differ depending on your Cloudbeds plan, the version installed and your property configuration. If in doubt, contact Cloudbeds support directly.

Signing in to your Cloudbeds account

Follow these six steps to open your Cloudbeds workspace, retrieve your API credentials and run a first synchronisation with your Cloudpmsbed modules.

Step 1 — Open the Cloudbeds access URL

Go to the URL Cloudbeds provided when your property was onboarded. It usually takes the form https://[yourhotel].cloudbeds.com or https://app.cloudbeds.com/[yourhotel]. If you cannot find it, the onboarding email from Cloudbeds contains it as well. Open the page in a recent browser (an up-to-date Chrome, Firefox or Edge) to avoid any certificate-related blocks.

Step 2 — Enter your administrator credentials

Enter your Cloudbeds identifier (typically the business email address attached to the property) and the password set at account creation. If two-factor authentication is enabled on your account, keep your authenticator app or SMS code ready before you submit. Cloudpmsbed has no access to your Cloudbeds password or your 2FA codes.

Step 3 — Open the Administration module

Once signed in, open the Administration or Settings menu depending on your version. Depending on the Cloudbeds release deployed on your account, the path may be: Administration → Integrations → API Access, Settings → External Integrations → Developer API, or Configuration → API → Generate Credentials. If no API entry is visible, your profile lacks the required rights — ask your property's main administrator to grant them.

Step 4 — Generate or retrieve your API key

In the API Access section, click "Generate a new key" or view the existing key. Copy the full key and the associated endpoint URL immediately: most Cloudbeds releases only reveal the key once. Store both values in an enterprise password manager, never in a shared text file.

Step 5 — Paste the credentials into Cloudpmsbed

Open your Cloudpmsbed Client Area, go to Settings → Connected Cloudbeds Account, and paste the API key and endpoint URL into the fields provided. Click "Test connection": Cloudpmsbed calls the Cloudbeds API and displays your property name, room types and detected permissions. This step does not yet change any data in Cloudbeds.

Step 6 — Activate modules and monitor connectivity

Once the connection is validated, activate each of the modules you need (Booking Engine Multi-Language, Channel Manager Sync, Guest CRM, and so on) individually from the Cloudpmsbed catalogue. The dashboard continuously shows the state of the Cloudbeds link and alerts you by email if synchronisation is interrupted. Review the permissions once a quarter to keep flows stable.

Common problems

The five incidents below account for the majority of the support requests received by Cloudpmsbed. Check the matching remedy before opening a ticket.

Forgotten password

Use the "Forgot password" link on the Cloudbeds access page. A reset email is sent to the address linked to your administrator profile. If the email does not arrive within 15 minutes, check the spam folder and confirm with your IT team that no filter is blocking the Cloudbeds sender domain. Cloudpmsbed cannot reset a Cloudbeds password on your behalf under any circumstances.

API key not visible

If the "API" entry does not appear in the Administration menu, your Cloudbeds plan probably does not include API access. Contact your Cloudbeds account manager to confirm eligibility. Another common cause: the key was generated by another administrator and never shared. Generate a new one and remove the old to preserve traceability.

Insufficient permissions

A "permission denied" error during the connection test means your key does not include all the required scopes. For most Cloudpmsbed modules you need at minimum: Read reservations, Read rates, Write rates, Read guest profiles and Write guest profiles. The PDF Invoicing module additionally requires read access to night-audit data. Edit the key in Cloudbeds to add the missing scopes and re-run the test.

Expired session

Cloudbeds automatically logs out inactive sessions after 30 minutes. If you are redirected to the authentication screen mid-configuration, sign in again and pick up at step 3: unsaved changes will be lost. For long operations (room mapping, rate plan imports) prepare all your data ahead of time and save regularly to avoid data loss.

Broken 2FA

If you have changed phones or lost access to your authenticator app, Cloudbeds requires a manual reset through its own support desk. Prepare your Cloudbeds property identifier and ID for the person named on the administrator account. The reset typically takes 24 to 48 business hours — do not disable 2FA permanently, it remains the strongest protection against credential theft.

Need help with your Cloudbeds account?

Cloudpmsbed supports users on the link between Cloudpmsbed modules and Cloudbeds. For issues internal to the Cloudbeds platform itself — password reset, plan upgrade to enable API access, questions about the available functionality — contact the Cloudbeds support desk directly on the official Cloudbeds website.

Cloudpmsbed support can be reached at support@cloudpmsbed.org or by phone on +382 20 872 619. Our team is available Monday to Friday, 09:00–17:00 CET, from our offices at ul. Meše Selimovića 14, 81000 Podgorica, Crna Gora. When writing about a Cloudbeds API connection, please include the email on your Cloudpmsbed account, the name of the affected module and the full error message shown in your dashboard.