– 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.
"first_name": "Jane", "last_name": "Doe", "email": "jane.doe@example.com", "phone": "+12125551234", "custom_fields": "dog_breed": "Labrador", "wine_preference": "Bordeaux" sevenrooms api documentation
https://sandbox.api.sevenrooms.com/v2/
Whether you are a developer building a custom integration for a 100-location restaurant group or a tech consultant advising a client, understanding these endpoints, authentication flows, and error codes will set you apart. Start in the sandbox, test your webhooks with ngrok, and always, always handle token refresh gracefully. – Lists all venues accessible to your API credentials
– Retrieve a specific guest by ID. GET /guests – List guests with pagination. Filter by email , phone , or updated_at range. POST /guests – Create a new guest. Required fields: first_name , last_name , and at least one contact method ( email or phone ). PUT /guests/guest_id – Update custom fields, tags, or dietary notes. Start in the sandbox, test your webhooks with
The future of hospitality is connected, real-time, and guest-centric. With the SevenRooms API documentation as your blueprint, you are ready to build it. Disclaimer: This article is based on publicly available information and the author’s experience. Always refer to the official SevenRooms API documentation provided by SevenRooms for the most current specifications, as endpoints and policies may change.