PPlatformAppStores

Cloudbeds Marketplace

Hospitality PMS and hotel operations integrations

Cloudbeds · General SaaS app marketplaces

Best for: Technology companies building integrations for hotels, hostels, short-term rentals, bed-and-breakfasts, inns, and other Cloudbeds property-management users, especially in operations, distribution, guest experience, payments, revenue, accounting, and hotel services.

Overview

Cloudbeds Marketplace is the first-party distribution surface for technology partners serving Cloudbeds property-management users. The ecosystem covers hotel and property operations, booking engines, channel management, guest communication, reputation management, payments, point of sale, revenue management, events, housekeeping, upsells, accounting, business intelligence, and access management. Cloudbeds presents the marketplace as a place where users can integrate tools and services, while its API and developer hub provide the technical starting point for integrations. The public marketplace page is marketing-led and does not expose a complete static catalog in the verified material, so no individual example apps or catalog-size claims are asserted.

The publisher path is structured around partnership review and certification. A technology partner submits a request, signs a Connectivity Agreement and, where required, a mutual NDA, receives partner credentials and a test account, then develops and tests the integration. Before certification, the partner submits app details, support content, images, and marketing materials and completes a certification call covering authentication, authorization, API behavior, and connection management. A passed certification leads to a limited release with five properties; successful validation then enables launch to all Cloudbeds users and Marketplace publication. Public sources do not specify fees, commissions, approval timelines, rate limits, or merchant-of-record treatment.

How to build & ship

  1. 1Submit a partnership request and complete Cloudbeds partnership review.
  2. 2Sign the Connectivity Agreement and, where required, a mutual NDA; obtain partner credentials and a test account.
  3. 3Develop and test against the Cloudbeds API using the documented authentication and connection flows.
  4. 4Submit app details, support documentation, images, and marketing materials, then complete the certification call.
  5. 5Run the required limited release with five properties and launch to all Cloudbeds users after successful validation.

Key APIs & SDKs

Hotel details and property data
Guest information
Rooms and reservations
Payments
REST API reference, GraphQL, and webhooks

Integration types

Connector
Embedded app

Authentication & security

  • Primary auth: API key
  • Also supports: OAuth 2.0
  • Security review: Not publicly specified
  • A formal security-review requirement is not established in the supplied public sources. Cloudbeds does document partnership review and certification checks for authentication, authorization, API calls, and connection or disconnection behavior; these should not be treated as a formal security certification requirement. Publicly available marketplace and developer materials do not specify a universal security-review requirement; confirm any partner-specific or product-specific review requirements with the platform. The reviewed public materials do not publicly specify a universal security-review requirement; confirm partner-specific or product-specific requirements with the platform. A universal security-review requirement is not publicly specified in the reviewed public materials; confirm partner-specific or product-specific requirements with the platform.
  • Cloudbeds reviews partnership applications, provides credentials and test access after the partnership step, and requires certification before limited release. Certification checks authentication, user authorization, API calls, and app connection/disconnection behavior. A limited release with five properties follows; after successful testing, the integration can be launched to all Cloudbeds users and published in the Marketplace.
  • Public documentation in the supplied package does not specify API rate limits.
Auth docs

Monetization

Onboarding
Not publicly specified
Commission
Not publicly specified
Merchant of Record
Not publicly specified

Pros & cons for builders

Pros

  • Clear first-party distribution route for hospitality integrations.
  • Documented API, developer hub, authentication options, webhooks, and integration guidance.
  • Structured certification and five-property limited-release process before broad availability.

Cons

  • Public sources do not provide a complete static Marketplace catalog.
  • Commercial terms, fees, commissions, and approval timelines are unspecified.
  • Certification and limited release add meaningful implementation and launch overhead.

Frequently asked questions

How do I get my app approved on Cloudbeds Marketplace?

Cloudbeds reviews partnership applications, provides credentials and test access after the partnership step, and requires certification before limited release. Certification checks authentication, user authorization, API calls, and app connection/disconnection behavior. A limited release with five properties follows; after successful testing, the integration can be launched to all Cloudbeds users and published in the Marketplace.

What authentication does Cloudbeds Marketplace use?

Cloudbeds Marketplace apps primarily authenticate with API key, also supporting OAuth 2.0.

How is Cloudbeds Marketplace monetized?

Cloudbeds Marketplace supports not publicly specified monetization. Typical commission: Not publicly specified. Onboarding fee: Not publicly specified.

Is a security review required to list on Cloudbeds Marketplace?

Cloudbeds Marketplace's public materials do not specify a universal security-review requirement. A formal security-review requirement is not established in the supplied public sources. Cloudbeds does document partnership review and certification checks for authentication, authorization, API calls, and connection or disconnection behavior; these should not be treated as a formal security certification requirement. Publicly available marketplace and developer materials do not specify a universal security-review requirement; confirm any partner-specific or product-specific review requirements with the platform. The reviewed public materials do not publicly specify a universal security-review requirement; confirm partner-specific or product-specific requirements with the platform. A universal security-review requirement is not publicly specified in the reviewed public materials; confirm partner-specific or product-specific requirements with the platform.