Sections
A section is a seating area — the terrace, the bar, a private room. This
resource lists the ones a guest can be asked to choose between, and the ids
section_id accepts on GET /v1/availability, POST /v1/reservations and
POST /v1/holds.
It needs the reservations:read scope. The fields, and why one area can appear
as several rows, are on The section object.
Endpoints
Section titled “Endpoints”| Endpoint | What it does |
|---|---|
GET /v1/sections |
The restaurant’s seating areas, one row per floor plan. |
Before you render a picker
Section titled “Before you render a picker”Two conditions decide whether the step exists at all. Group the rows by
group_id first — The section object
says why, and which row names the group. Then check show_seating_preference on
GET /v1/configuration, which is the
restaurant saying whether it wants guests asked.
Book a whole room uses the same ids to take every table in an area.