https://sandbox.api.sevenrooms.com/v2/
– Lists all venues accessible to your API credentials. Returns venue_id , name , timezone , and address . GET /venues/venue_id/configuration – Retrieves venue-specific settings like table layouts, section names, and seating durations. 4. Waitlist ( /waitlist ) Real-time waitlist management requires webhooks (more on that later), but polling is also possible. sevenrooms api documentation
– Fetch reservations within a date range. Supports query params: start_date , end_date , venue_id , status (e.g., confirmed , seated , completed ). POST /reservations – Create a booking. You must reference an existing guest_id or create a guest on the fly using nested objects. DELETE /reservations/reservation_id – Cancel a reservation (requires a cancellation_reason parameter in the body). https://sandbox
This is where the comes into play. For developers, technical product managers, and systems integrators, understanding the SevenRooms API documentation is the first step toward building seamless, real-time hospitality ecosystems. Supports query params: start_date , end_date , venue_id
"data": [...], "pagination": "next_cursor": "abc123def456", "previous_cursor": null, "limit": 50
For now, the REST v2 API is stable, well-documented, and actively maintained. Always refer to the official docs at https://docs.sevenrooms.com/api (note: this requires partner login credentials). The SevenRooms API is a powerful gateway to one of hospitality’s most sophisticated guest data platforms. But power comes with responsibility. The official documentation is your best friend—read it carefully, respect rate limits, and design for idempotency.