The "story" of the SevenRooms API is about turning a simple restaurant reservation into a comprehensive, data-driven guest profile. By using the API, developers can go beyond just booking a table, creating a system that tracks a guest's entire journey from the first click to the final payment. What You Can Build
1. Receive POST /webhook/reservation-created
2. Verify signature
3. Extract reservation and guest data
4. Upsert guest in DB (match by email or phone)
5. Save reservation linked to guest
6. Send confirmation via email provider
One key detail buried in the docs: SevenRooms does not use OAuth 2.0 out of the box for standard integrations. Instead, they rely on API keys sent as Bearer tokens. sevenrooms api documentation
: Accessing and building detailed guest profiles and history. : Retrieving guest feedback and reviews. Widget Integration The "story" of the SevenRooms API is about
| Method | Endpoint | Description |
|--------|----------|-------------|
| GET | /reservations | List reservations with filters (date, status, venue_id) |
| GET | /reservations/id | Get single reservation by ID |
| POST | /reservations | Create a new reservation |
| PUT | /reservations/id | Update an existing reservation (e.g., party size, time) |
| DELETE | /reservations/id | Cancel reservation | Authentication Method: Bearer Token (No OAuth 2
The SevenRooms API documentation is well-structured and organized, making it easy for developers to navigate and find the information they need. The documentation is divided into several sections, including: