The API lets another system check your availability and make, look up and cancel bookings for your business, without anyone on your team typing them in. This article explains who should have access, how to give it, how much to share, and how to take it away again.
What it is 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 for you. A booking made this way follows the same rules as one a guest makes online: it needs a free table at a time you offer, takes a deposit if you ask for one, and sends the usual confirmation and alerts. It shows in your diary with the source API.
Before you begin
- You need to be an owner or admin on the business.
- Only give access to a company you have an agreement with. You are choosing to share booking data, and possibly guest details, with them, and your privacy notice should say so. See the API section of our terms.
Giving a system access
- Sign in to manage.makearezzy.com and pick your business.
- Open Integrations from the left-hand menu and choose API access.
- Type a name for the system, such as "Harbour Hotel front desk", and select Add client. Use one client for each system.
- Select Issue key, choose what the key can do, tick the confirmation, and select Issue key.
- Copy the key and pass it to the partner privately.
Choosing what a key can do
Start from one of the ready-made choices and share as little as the partner needs.
- Read only — see your business name and time zone, check availability, and look up a booking.
- Limited — all of that, plus make bookings, change the guest's details and notes on them, and cancel them. This suits most partners.
- Full — all of that, plus read guest names, contact details and special requests, and reach bookings the partner did not make.
- Custom — tick exactly what you want.
Changing what a key can do
Select Edit beside a key, choose what it can do, tick the confirmation, and select Save changes. The change takes effect straight away. The key itself stays the same, so the partner does not need a new one. A revoked key cannot be changed.
Things worth knowing
- A key cannot overbook, skip a deposit, pick a table or change a booking's time. To move a booking, the partner cancels it and books again.
- If a partner sends a guest's name, email or phone number slightly differently from the last time, a second guest profile is created. You can join them up afterwards; see Merging duplicate guests.
- Each client can make up to 120 requests a minute, shared by all of its keys.
Taking access away
Select Revoke beside a key to stop that key, or Revoke client to stop every key the system holds. It takes effect straight away and cannot be undone. Bookings already made are kept. Revoked clients and keys stay on the page so that you have a record.
Seeing who changed what
Open Change history under a client to see when each key was issued, changed or revoked, and by whom.
For the partner's developer
The API reference lists every request with examples in curl, Python and JavaScript.
Where to go next
- Deposits and refunds — the deposit rules a booking made through the API follows.
- Marketing consent — a key cannot opt a guest in to marketing.
- Alerts and emails — the alerts your team gets for new and cancelled bookings.