SevenRooms API enables hospitality operators to unify their guest data by connecting the platform to over 100 third-party tools, including point-of-sale (POS) systems, marketing platforms, and website widgets
API Flow:
- Guest Management: Create, update, and retrieve guest profiles, including dietary preferences, custom fields, and contact information.
- Reservations: Fetch real-time booking data, create new reservations, modify existing ones, or cancel them.
- Waitlists: Manage the virtual waitlist, including seating guests, estimating wait times, and syncing with front-of-house displays.
- Marketing & Loyalty: Track email opt-ins, SMS consent, and loyalty tier memberships.
- POS Integration: Sync check totals, item-level details, and payment statuses (often used with partners like Toast, Square, or Oracle).
Options to proceed:
-
- Purpose: Link reservations to pre-orders or on-site charges.
- Use cases: Prepaid menus, deposit handling.
- Mock data (you can create and delete freely).
- Lower rate limits (50 per 10 seconds) to discourage abuse.
- A test dashboard to manually create events.
💡 The docs do a decent job showing sample responses, but check for pagination headers—some endpoints default to 50 records per page.
Important Security Notes from the Docs
- Never expose
client_secret in client-side code (e.g., mobile apps or web browsers).
- Implement a token refresh mechanism before expiry. The API returns a
expires_in field (usually 3600 seconds).
- Use HTTPS exclusively; the SevenRooms API rejects all non-TLS requests.
POST /guests – Creates a new guest profile. Required fields: firstName, lastName, email, or phoneNumber.GET /guests/guestId – Fetches a guest’s complete history, tags, dietary restrictions, and loyalty status.PUT /guests/guestId – Updates guest metadata. Common use: Syncing custom fields from an external CRM (e.g., "Favorite Wine: Malbec").POST /guests/lookup – Searches for a guest by email or phone. Always call this before creating a new guest to avoid duplicates.
Sevenrooms Api Documentation [ AUTHENTIC - 2026 ]
SevenRooms API enables hospitality operators to unify their guest data by connecting the platform to over 100 third-party tools, including point-of-sale (POS) systems, marketing platforms, and website widgets
API Flow:
- Guest Management: Create, update, and retrieve guest profiles, including dietary preferences, custom fields, and contact information.
- Reservations: Fetch real-time booking data, create new reservations, modify existing ones, or cancel them.
- Waitlists: Manage the virtual waitlist, including seating guests, estimating wait times, and syncing with front-of-house displays.
- Marketing & Loyalty: Track email opt-ins, SMS consent, and loyalty tier memberships.
- POS Integration: Sync check totals, item-level details, and payment statuses (often used with partners like Toast, Square, or Oracle).
Options to proceed:
-
- Purpose: Link reservations to pre-orders or on-site charges.
- Use cases: Prepaid menus, deposit handling.
- Mock data (you can create and delete freely).
- Lower rate limits (50 per 10 seconds) to discourage abuse.
- A test dashboard to manually create events.
💡 The docs do a decent job showing sample responses, but check for pagination headers—some endpoints default to 50 records per page. sevenrooms api documentation
Important Security Notes from the Docs
- Never expose
client_secret in client-side code (e.g., mobile apps or web browsers).
- Implement a token refresh mechanism before expiry. The API returns a
expires_in field (usually 3600 seconds).
- Use HTTPS exclusively; the SevenRooms API rejects all non-TLS requests.
POST /guests – Creates a new guest profile. Required fields: firstName, lastName, email, or phoneNumber.GET /guests/guestId – Fetches a guest’s complete history, tags, dietary restrictions, and loyalty status.PUT /guests/guestId – Updates guest metadata. Common use: Syncing custom fields from an external CRM (e.g., "Favorite Wine: Malbec").POST /guests/lookup – Searches for a guest by email or phone. Always call this before creating a new guest to avoid duplicates.