Sevenrooms — Api Documentation

Unlike some SaaS platforms that put docs behind a login wall, SevenRooms provides public API documentation (typically hosted at developers.sevenrooms.com or via a dedicated Swagger UI).

You’ll need:

Pro tip: SevenRooms uses API keys tied to specific Venues or Portfolio level access, so clarify your scope before writing a single line of code. sevenrooms api documentation

Below are the most critical endpoint groups from the official docs.

Goal: Identify which marketing channel (Google Ads, Instagram, Email) generated a reservation. Unlike some SaaS platforms that put docs behind

API Flow:

The guest object is the atomic unit of SevenRooms. Every diner, walk-in, or regular gets a guest_id. Pro tip: SevenRooms uses API keys tied to

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"