Access rich guest profiles—dietary notes, visit frequency, lifetime value, birthday, and preferences. Write access allows you to enrich profiles from external surveys or loyalty apps.
Restaurants with high walk-in traffic can use this to sync waitlist status with a digital signage app, SMS provider, or host pager system.
The guest object is the atomic unit of SevenRooms. Every diner, walk-in, or regular gets a guest_id. sevenrooms api documentation
GET /guests/guest_id – 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.
Example Payload (POST):
"first_name": "Jane",
"last_name": "Doe",
"email": "jane.doe@example.com",
"phone": "+12125551234",
"custom_fields":
"dog_breed": "Labrador",
"wine_preference": "Bordeaux"
Here's what I can do to assist you:
While this article focuses on REST, whispers in the SevenRooms developer community mention a GraphQL API in beta. The official documentation hints at this under "Experimental Features." GraphQL would allow integrators to fetch exactly the fields they need (e.g., only guest name and last visit date) without over-fetching. "first_name": "Jane", "last_name": "Doe", "email": "jane
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).