Availability
Availability answers what was sellable at the moment you read it. It is a
projection and not a promise: POST /v1/reservations and POST /v1/holds
re-check every cap and every table fit under a lock, so a slot you were shown
can still be refused.
Both endpoints need the reservations:read scope. The two shapes are on The
availability object.
Endpoints
Section titled “Endpoints”| Endpoint | What it does |
|---|---|
GET /v1/availability |
Per-shift slots for one service date and one party size, optionally filtered to a seating area. |
GET /v1/availability/months |
Which days are worth opening, for every party size at once. No party size, no section. |
Two grains, two questions
Section titled “Two grains, two questions”The month endpoint answers “which days should the calendar offer”, and it is filter-independent on purpose: one read paints a whole month for every party size. The day endpoint answers “which times, for this party” and is the one that carries covers, shifts, closures and card guarantees.
Build a booking funnel uses both in order.