Use the Guesty Open API to read and send guest conversation messages
domain: open-api-docs.guesty.com · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Retrieve a reservation via the reservations API, then use its associated conversation ID to fetch the message thread via GET /v1/communication/conversations.
Send an outbound guest message with POST /v1/communication/conversations/{conversationId}/send-message.
Subscribe to the messages webhook to be notified whenever a new message is sent to a guest from the Guests Inbox, Owners Inbox, or via the API itself.
On an inbound message webhook, use the reservation ID in the payload to look up the reservation, then pull its conversation ID to retrieve full message history.
Account for channel-specific delivery quirks: owner conversations don't support the airbnb2 module type, and messages tagged with the "platform" module type are actually delivered via email.
Known gotchas
Owner conversations have narrower channel support than guest conversations, so a messaging flow built for guests may not work unmodified for owner communications.
Messages using the "platform" module type are routed through email under the hood, which can surprise integrations expecting native in-app/OTA delivery.
Resolve the conversation ID via the reservation each time rather than caching it indefinitely, since conversations are tied to current reservation state.
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?