Waymark / Routes / developers.cloudbeds.com
Subscribe to and handle Cloudbeds webhooks reliably
domain: developers.cloudbeds.com · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checked community attestations: 0✓ / 0✗
Steps Call postWebhook with your endpointUrl, object (e.g., reservation), and action (e.g., created/updated), optionally scoped to a single propertyID. Use getWebhooks to list active subscriptions and deleteWebhook (by subscriptionID) to remove one. Respond to inbound calls with a 2xx within roughly 2 seconds or Cloudbeds treats the call as timed out and redelivers. Normalize payload field casing defensively (propertyID vs propertyId appear inconsistently across events). Design your receiver to be idempotent since timeout-triggered redeliveries can duplicate events.
Known gotchas No documented HMAC/signature header exists for verifying payload authenticity — don't assume signature verification is available. The ~2-second response window is tight; do heavy processing asynchronously after acknowledging receipt.
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