Your operation, available for whatever you want to build on top
An API with keys per property, signed events and public documentation.
Catalog, orders, reservations, availability, customers and cash movements, available to read and write from your own system. With keys per property, signed events and a sandbox to build without touching the live operation.
What you can read and write
Catalog, orders, reservations, availability, customers and cash movements. With keys per property, so an outside developer never has access to more than what belongs to them.
- Catalog, orders and reservations
- Availability, customers and cash movements
- Keys per property
Live events
Your system finds out when something you care about happens: a closed check, a room charge, a closed cashier shift, a reservation created or cancelled. Signed, so your server can verify they came from us and not from someone else. No need to keep asking every minute.
- Closed check, room charge, closed shift
- Reservation created or cancelled
- Signed: your server verifies they came from us
What is already connected
Payment gateways, the online travel agency connector, messaging, and the maps and review platforms where your hotel already appears. The full list lives on its own page and is kept up to date; we never promise an integration that is not released.
- Payment gateways
- Online travel agency connector and messaging
- Maps and review platforms
Who uses this
- The group that wants its own corporate dashboard, with its own design.
- The one connecting accounting who never wants to key in a journal entry again.
- The one who already has inventory or payroll and has no plans to change them.
- The developer building something on top of their clients’ operations.
Developer portal
Reference, examples, test keys and a sandbox, at https://r2developers.com. Whoever needs it finds it there.
Your restaurant already sells. Your system just does not know it.
Fifteen minutes, with your menu and your tables. Nothing to install.