The RevasiPartner API.
Read-only REST access to reservations and guests at your venues, for the CRM and analytics tools your group already runs. Scoped keys, a sandbox on demo venues, and an OpenAPI document for every endpoint.
GET /api/v1/reservations?date_from=2026-10-10&date_to=2026-10-10Authorization: Bearer rv_test_••••••••Demo only: sample data and simplified responses. The API reference has every field.
- Get a key.Log in to Revasi. Start with a sandbox key: it reads only the demo venues.
- Make a request.Send the key as a Bearer token, exactly as in the console above.
- Page through.Pass next_cursor back as ?cursor= until it comes back null.
- Go live.Swap in a live key. Nothing else changes.
Ask about your reservations in plain language.
MCP is the open standard AI assistants such as Claude and ChatGPT use to work with other software. Revasi’s MCP server will give an assistant the same read-only access to your reservations and guests as the Partner API, with no integration code to write.
It will be the first official MCP server from a reservation system in Southeast Asia.
Talk to us- No integration to build.The assistant reads what each tool does and calls it when a question needs it. There is nothing to code or host.
- Read-only, by design.It can look at bookings and guests. It cannot create, change or cancel anything on your floor.
- Your key, your venues.The same scopes and the same 60-a-minute limit as the Partner API, so an assistant only ever sees what its key allows.
- Errors it can act on.Every failure comes back with a code and a hint, so the assistant corrects itself instead of guessing.
How many covers did we seat last Saturday, and how many added the wine pairing?
{
"date_from": "2026-10-03",
"date_to": "2026-10-03",
"status": [
"SEATED",
"PARTLY_SEATED",
"LEFT"
]
}You seated 86 covers across 31 bookings last Saturday. 11 of those bookings added the wine pairing, for 19 guests.
What you can read.
Four endpoints, all read-only, all scoped to the outlets on your key. Structured dietary fields and private operator notes are never exposed.
| Endpoint | Scope | Returns |
|---|---|---|
| GET /api/v1/guests | read:guests | Guests with a booking or waitlist entry at your outlets. |
| GET /api/v1/guests/{id} | read:guests | One guest, with visit history and waitlist entries. |
| GET /api/v1/reservations | read:reservations | Reservations, filtered by date, outlet, status or guest, with updated_since for sync. |
| GET /api/v1/reservations/{id} | read:reservations | One reservation, with attribution, payment, estimated value and upgrades. |
- GET /api/v1/guestsread:guestsGuests with a booking or waitlist entry at your outlets.
- GET /api/v1/guests/{id}read:guestsOne guest, with visit history and waitlist entries.
- GET /api/v1/reservationsread:reservationsReservations, filtered by date, outlet, status or guest, with updated_since for sync.
- GET /api/v1/reservations/{id}read:reservationsOne reservation, with attribution, payment, estimated value and upgrades.