Consume Smoobu webhooks for calendar and reservation changes
domain: support.smoobu.com · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Set your webhook URL in the Smoobu account's API/webhook settings; Smoobu POSTs a JSON payload when rates, availability, or reservations change.
Treat each inbound POST as a "something changed" signal and use the apartmentId/reservation identifiers in the payload to call the corresponding GET reservations or GET rates endpoint for authoritative current values.
Log every inbound delivery so you can reconcile against a periodic full poll if a delivery is dropped.
If you're a certified third-party provider, confirm whether you're using the aggregated multi-user webhook path versus a single-account webhook URL, since these are separate setup paths.
Build idempotent processing since Smoobu's webhook docs don't describe a payload-signing scheme comparable to its HMAC request signing.
Known gotchas
Smoobu does not document a webhook payload-signature verification header the way it does for HMAC-signed requests — don't assume a signing scheme is present without testing against your own account.
There's no documented automatic retry/replay if your endpoint is briefly unreachable, so pair webhooks with periodic polling rather than relying on them exclusively.
Third-party-provider (multi-account) webhook access is a separate, gated integration path from a single customer's webhook URL — confirm which one your integration actually needs.
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?