To use the SevenRooms API, developers must authenticate their requests using one of the following methods:
No API documentation is complete without discussing constraints.
Before writing a single line of code, you need access to the official resources. Unlike some public APIs (e.g., Twitter or Google Maps), SevenRooms takes a partnership-driven approach. sevenrooms api documentation
Based on the documentation’s examples, here are three common integration patterns.
All requests are made to:
https://api.sevenrooms.com/v1/
The API versions via URL path (/v1/, /v2/ planned). Breaking changes are announced with 6 months notice.
This is the heartbeat of the API.
GET /reservations – 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).
Critical Limits (per docs):