domain: developers.cloudbeds.com · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Register an app in the Cloudbeds developer portal and obtain an API key (currently the recommended auth method), or use OAuth2 authorization-code flow as an alternative.
Call getSources to find or create the sourceId for your integration if you don't want bookings attributed to the default "Website/Booking engine" source.
POST to /api/v1.3/postReservation with guest, room, and rate details, including sourceId and an optional thirdPartyIdentifier for reconciliation.
Confirm the reservation was created by reading it back or listening for a corresponding webhook event.
Target API version v1.3 for new integrations — v1.1 was deprecated March 31, 2025 and v1.2 is legacy-but-listed.
Known gotchas
API keys are now the primary documented auth method; Cloudbeds publishes a dedicated OAuth2-to-API-Key migration guide signaling where new integrations should go.
Omitting sourceId silently attributes bookings to the default booking-engine source, which can skew reporting.
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?