While SevenRooms does not publish its exact rate limits, you should assume that each API key has a reasonable quota. Implement request throttling in your integration, and if you expose the integration publicly, add your own rate‑limiting layer to protect your backend systems.
( GET /guests , POST /guests )
By following the SevenRooms API documentation, you can integrate their powerful hospitality CRM features into your custom applications and unlock new possibilities for your business. sevenrooms api documentation
POST /waitlist , DELETE /waitlist/waitlist_id Events & Ticketed Experiences
platforms that abstract away the differences between multiple hospitality systems (e.g., OpenTable, Yelp, Resy, and SevenRooms). With a unified API, you implement one set of booking endpoints that work across many platforms, reducing development time but potentially limiting access to platform‑specific features. While SevenRooms does not publish its exact rate
Cache venue details, floor plans, and user configurations locally. Do not request them for every reservation look-up.
: Search for guests using filters like email, phone number, or name. Do not request them for every reservation look-up
Every reservation created, modified, or cancelled in SevenRooms is exposed through the API. Reservation data includes: