Book real tables
from your app
The Reservations API finds open times and books them on each person's own reservation account, then checks that account to prove the table is theirs.
One API for OpenTable and Resy. Your app never has to learn either one.
OpenTable
Open times, booking and cancelling, all on the person's own account.
- Open times
- Book
- Cancel
- Booking status
Resy
The same calls and the same answers, so your app writes one integration.
- Open times
- Book
- Cancel
- Booking status
Connect once, in your app. Your screens, their own account.
- They connect their accountOnce, in your app. They give the phone on their account and the code the provider texts them.
- Your app finds a timeOpen times come back for the night and party size they asked for.
- Layout reads the termsThe deposit, the cancellation fee and whether a card is needed, from the restaurant itself.
- They say yes, and it's bookedUnder their own name, on their own account, and reported as booked only once it shows up there.
Every fee, before anything is booked. Nothing with a cost books without a yes.
No deposit
A table with no deposit and nothing owed for cancelling books as soon as the person asks for it.
Table for 2
WhenFriday, 7:30 PM DepositNone CancellationFree BookA deposit or a card
Your app shows the restaurant's own terms and the card it holds. Layout books only after the person says yes.
Table for 4
WhenSaturday, 8:00 PM Deposit$25 per person Late cancellation$50 per person CardVisa ending 4242 Confirm and bookBooked means it's on their account. Not that a button was pressed.
Booked
The restaurant confirmed it and it shows on the person's own account.
Checking
When an answer comes back unclear, Layout reads their account instead of trying again, so nobody is booked twice.
Cancelled
Cancelled through the same account, and reported only once it's gone from it.
Questions, answered
Yes, their own. Your app connects it once with the code the provider texts them, then books on it only when they ask.
Restaurants that take reservations on OpenTable or Resy. Not every restaurant uses them, so keep a fallback, such as a link to the restaurant's own site.
No. Your app passes along the code the provider texts, once. The sign-in it creates is encrypted and kept by Layout, and your app never sees a password or a session.
The Reservations API is in early access. Book an intro call and we'll set up your app.