Published OpenAPI 3
Documented error codes, a changelog and examples. Idempotent reservation creation.
Product · API and webhooks
For the guest app, the lobby kiosk or the chatbot.
Availability, reservations and signed events under a stable contract. The same API key scopes what an integrator can do and what an AI assistant can do.
Included in the plans with the public API.
Contract
What an integrator expects to find.
Channel rules
Minimum notice, daily cutoff and cancellation window per seating apply to the app channel; the concierge keeps their override.
Signed webhooks
reservation.created, updated and cancelled with an HMAC signature, exponential retries and automatic deactivation after ten failures.
Per-integrator quotas
Cap the share of the daily capacity a channel may sell, so the concierge never runs out of inventory.
AI assistants (MCP)
An MCP server at mcp.mesatto.com: curated tools (hotels, policies, availability, guest, reservations) for Claude, ChatGPT, Copilot or your own agent. Same key, same scope, confirmed writes.
Its own channel in the reports
What comes in through the API shows as such: occupancy and no-shows per channel, never mixed with the concierge.
Frequently asked questions
- Where is the documentation?
- At /api/docs: OpenAPI 3 with examples, error codes and a changelog.
- How does it authenticate?
- With Authorization: Bearer and an API key issued from the dashboard, scoped by hotel, restaurant and permission.
- Which events do the webhooks emit?
- reservation.created, reservation.updated and reservation.cancelled, HMAC-signed and with retries.
- Can I cap how much a channel sells?
- Yes: per-integrator quotas as a share of each restaurant's daily capacity.