Use cases

Each guide below starts from an integration you are building, then walks the calls it needs and the refusals it has to handle. Endpoint detail stays in the API reference; the conventions every guide relies on are in Pagination, Errors and Rate limits.

• Build a booking funnel: Rebuild the booking flow on your own pages — availability, seating, the create call, and the refusals a funnel has to render.
• Hold a slot: Claim a table while a package is assembled or a payment clears, then convert the hold into the booking or hand it back.
• Change a held time: You hold one time and the guest wants another. Take a new hold, then release the old one, and read availability without your own hold in the way.
• Book past the rules: Waive a booking rule for a corporate dinner, a VIP or a party of thirty — what can be waived, what can never be, and what the restaurant sees afterwards.
• Book a whole room: Take every table in a section for a corporate dinner or a private event in one call — find the room, book it, and handle a room that is partly taken.
• Keep your system in sync: Mirror a restaurant's bookings into your own CRM — webhooks for the signal, updated_since for the truth, ETags for the cost.
• Take a deposit: Book a slot that asks the guest for a card — what you can see, what you cannot build, and the two refusals that surprise people.