For the salon owner's developer, or the owner who is one

A salon booking API and webhooks, included with every account

Sooner or later a growing salon wants its booking data somewhere else: a Google Sheet the manager lives in, a dashboard on the break-room TV, a CRM that sends the birthday postcard, a custom website that shows today's openings. Slotora has a JSON API and signed webhooks for exactly that, at no charge and without a developer program to join. An owner creates a key in settings and decides what it may touch.

Create an account and an API key

What the API gives you

Four scopes. A key gets the three read scopes unless you change them; making bookings is off until you check it.

Read bookings

Appointments between two dates, today and the next 31 days unless you ask for a range of up to 366. Filter by status, by stylist, by location, or by what changed since your last call.

Read clients

Names and, while your salon shows contact details to the team, phone numbers and emails, by date created or updated. Notes, warnings, addresses, birthdays and tags are never sent.

Read services, staff and locations

The menu with durations and prices, the team, and your addresses, so an outside tool can label what it pulls.

Make bookings

Off by default. With it on, a tool can book only the times your own booking page would offer: no overriding a closed slot, no recurring series, no custom price.

Keys, limits and the privacy line

The facts a developer asks for first.

How Slotora's API keys and limits work
QuestionAnswer
Who can create a key?The owner or an admin, in the browser under settings.
How many keys?Up to 20 active keys per salon. Make one per tool, so you can switch one off without breaking the rest.
How is it sent?In a header: Authorization: Bearer, or X-Api-Key. Never in the URL.
How fast?120 requests a minute per key. Above that the answer is HTTP 429 with a Retry-After header.
Paging?Cursor pages of up to 100 records.
When does a key die?When you revoke it, or when the person who made it stops being an owner or admin.
Can it double-book?No. A booking made through the API runs the same checks as the front desk. Send an Idempotency-Key and a retried request will not book twice.

The key is shown once, when you create it. Slotora stores only a fingerprint of it, so a lost key is replaced, not recovered.

Webhooks: Slotora calls you

Five events, delivered to an https address you give, signed so you can tell the call is really from Slotora.

  1. Events

    Bookings, clients and payments

    A booking created, changed or canceled, a new client, and a payment recorded. Each delivery says which and carries the record.

  2. Timing

    Within about 15 minutes

    Slotora collects events in a sweep that runs roughly every quarter hour. Webhooks are for keeping systems in step, not for a buzzer that rings the second a client books.

  3. Proof

    A signature on every call

    The Slotora-Signature header carries a timestamp and an HMAC-SHA256 of the timestamp and the body, made with your endpoint's secret. Check both and reject anything old.

  4. Failures

    Retries, then a warning

    A failed call is tried again after 1, 5 and 30 minutes, then 2, 6, 12 and 24 hours. After 15 failures in a row, or three days of them, the endpoint is switched off and the owner gets a notification.

Zapier, Make and the spreadsheet your manager wants

There is no Slotora app in Zapier's or Make's directory yet. Both connect anyway. In Zapier, a Webhooks by Zapier trigger with Catch Hook gives you an address to paste into Slotora as an endpoint; every new booking then arrives as a Zap you can send to Google Sheets, Slack or a mailing list. Zapier's own help page lists Catch Hook on its Professional, Team and Enterprise plans, not on Free.

Make works the same way with its webhook module, and either tool can call the API back with an HTTP step and your key when it needs more than the event carried.

The full reference, with every field and error, is the OpenAPI file at slotora.io/api/v1/openapi.json. Its examples are written in pounds; a US salon's amounts come back marked USD, in cents (4500 is $45.00).

What the API is not

Not instant
Webhooks run on a sweep of about 15 minutes. If you need a client to see her booking the second she makes it, that is what the booking page and its emails are for.
Not a back door to the private parts
Client notes, allergy and caution flags, birthdays and addresses never leave through the API, whatever the scope.
Not an accounting connection
There is no built-in QuickBooks or Xero sync behind it. A payment webhook gives a developer what is needed to build one.

API questions

Does the API cost extra?

No. Keys, calls and webhooks are free, within the limit of 120 requests a minute per key.

Can I build my own booking widget on the API?

Yes, with the make-bookings scope switched on. It will only offer and accept the times your own booking page would, so the rules you set still hold.

Is there a Zapier integration?

Not a listed app yet. Use Webhooks by Zapier with Catch Hook as the trigger and paste its address into Slotora as a webhook endpoint. Check Zapier's plan: Catch Hook is not on its free plan.

Can a stylist create an API key?

No. Only the owner or an admin can, and a key stops working if the person who made it loses that role.

Which time zone do booking times use?

Your salon's own. A booking's start comes back as an ISO 8601 time in the salon's time zone with its offset, beside the date as the salon sees it. Every location in an account shares that zone.

Source

Read on November 19, 2026. Zapier sets its own plans and may change them.

  1. Zapier Help Center — Trigger Zaps from webhooks — https://help.zapier.com/hc/en-us/articles/8496288690317-Trigger-Zaps-from-webhooks · Read on Catch Hook; plan availability.

Your data, where you want it

Sign up, open settings, create a key with only the scopes the tool needs, and add a webhook endpoint if you want Slotora to call you.

Sign up free

May we measure which pages actually help? “Accept all” also lets us measure our own adverts.

What exactly does this mean?

We'd like to use Google Analytics to see which pages help and which don't, and to remember which poster, flyer or message of ours — or which salon's recommendation — brought you here. Accept all also allows a Meta advertising pixel, so we can tell which of our own adverts brought a salon that signed up — and if you create an account, our server sends Meta your email address scrambled (hashed), never as readable text, with your IP address, your browser's details and Meta's own cookie ids — never your name — purely so it can recognize that the sign-up came from an advert. None of this runs on a salon's own booking page. Everything the service itself needs works either way. Cookie Policy