A restaurant booking API that connects the systems you already use

Let a hotel desk, a ticketing system or your own developer check availability and make bookings in your restaurant, under the same rules as your website. More bookings from more places, and nobody re-typing a thing.

Book a 30-minute walkthrough

Included in every account. $1.25 per cover, no subscription.

Booking from

An example booking, to show how it reads.

More ways for guests to book you

  • Hotel desks book dinner for guests

    A front desk can check your availability and book a table for a # guest in the middle of a conversation, with no phone call and no re-keying via their own integrated system.

  • Ticketing systems add a table to a show

    Let theatre-goers book dinner as part of buying their tickets, and the booking lands in your diary ready to seat.

  • Your own developer, your own ideas

    Build exactly the booking experience you want, from your own app to a tool for your team, on top of the same system your restaurant already runs on.

Open, and still in your control

You decide who connects and exactly what each system can do. Every booking they make follows the same rules as one made on your own website.

The connected system can even tell you where the guest came from, so you can see which partners bring you the most bookings.

Your rules, every time
A free table, a time you offer, a deposit if you ask for one and the usual confirmation for your guest.
You choose what each system can do
Share as little or as much as a partner needs, with guest details kept private unless you decide otherwise.
Stop it in a click
Take a system's access away whenever you like, and it stops straight away.

For your developer

Every request is documented, with examples in curl, Python and JavaScript.

Read the API reference

Questions about the booking API

What can a connected system do?

Check your availability, then make, look up and cancel bookings for your restaurant, without anyone on your team typing them in.

Who is it for?

A hotel front desk system booking dinner for a guest, a ticketing system adding a table to a show, or your own developer building something just for you.

Do these bookings follow my normal rules?

Yes. A booking made this way needs a free table at a time you offer, takes a deposit if you ask for one and sends your guest the usual confirmation, just like one made on your website. It appears in your diary marked as coming from the API.

How do I give a system access?

An owner or admin adds the system from the Integrations area of the management app and issues it a key, choosing what that key can do.

Can I control what a partner can see?

Yes. You choose what each key can do, and guest details stay private unless you decide to share them.

Can I stop a system's access?

Yes. Revoke a key or a whole system in a click and it stops straight away. Bookings already made are kept.

Where does a developer start?

The API reference lists every request with examples in curl, Python and JavaScript.

What else Make a Rezzy does

See it working for your restaurant

Tell us which systems you'd like connected and we'll show you how the API can bring you bookings from them.

Book a 30-minute walkthrough

Developers, read the API reference. Or see every feature.