What we do
Tools
Industries
Department
How we workLet's talk →
Home/Acuity/Acuity API Access, Webhooks and the Premium Plan
Acuity Scheduling

Before Your First Acuity API Call: The Plan, the Two Credentials and the Server Rule

The business wants each booking in its CRM or practice system, and you've been handed an Acuity login. Three things decide whether your first call works: the account's plan, a user ID paired with an API key, and running the code on a server, because Acuity refuses calls from the browser.

What a working setup needs

Plan: API access sits on Acuity's Premium plan (called Powerhouse before the rename). Check the account's plan before writing any code.

Credentials: your numeric user ID and API key, both on the Integrations page. Send them as HTTP Basic auth, user ID as the username and key as the password.

Integrations API

Requests: calls go to https://acuityscheduling.com/api/v1/, for example /appointments. Make them from a server. Acuity doesn't allow cross-origin calls, since they'd expose the key.

Building for many Acuity accounts? Use OAuth2 instead of collecting each business's key.

Built in, Zapier, or the Acuity API?

The job Reach for Why that one
A Zoom link on each video appointment The built-in Zoom connection Acuity creates and attaches the link itself once Zoom is connected.
Bookings on your Google Calendar, and busy times blocked Acuity's own calendar sync Set up in Acuity's settings, separately from the API.
A deposit or full payment at booking The built-in Square, Stripe or PayPal connection The payment is tied to the appointment without any code.
A new or canceled booking starts one step in another tool Acuity's Zapier app Fine for single steps. It gets fragile once updates have to flow both ways.
Two-way sync with a CRM, franchise or practice system Zapier doesn't reach The API plus webhooks Needs a server, the Premium plan, and someone to own the code.

Why an Acuity integration works in testing and misses bookings later

Expecting the whole appointment in the webhook

How you'll know: Your listener gets an event with an appointment ID and little else.

Fix: Acuity keeps that payload thin on purpose. Call GET /appointments/{id} with your credentials to fetch the details, intake answers included, then act on them.

Calling the API from a booking page script

How you'll know: Requests fail in the browser, or the API key ends up in page source.

Fix: Move the calls to a small server and expose only the endpoint your page needs.

Trusting any POST to the webhook URL

How you'll know: Anyone who finds the URL could fake a booking.

Fix: Check the X-Acuity-Signature header, a base64 HMAC-SHA256 of the body keyed with your API key, before doing anything.

Running out of webhook slots

How you'll know: Creating another webhook through the API returns a 400.

Fix: An account can hold at most 25 API-created webhooks. Point one per event at a single listener that fans out, rather than one per downstream tool.

Assuming webhooks cover the past

How you'll know: The new system has bookings from launch day forward and nothing before.

Fix: Webhooks only report what happens after they're set up. Pull history once through the appointments endpoint, calendar by calendar, before you switch.

One booking, from Acuity into your other system

  1. 1

    Register the webhook

    POST to /webhooks with an event, such as appointment.scheduled, and your target URL. The target must be on port 443 or 80. Add appointment.rescheduled, appointment.canceled and appointment.changed if the other system needs to stay in step.

  2. 2

    Verify and fetch

    Check the signature, take the appointment ID, and fetch the full appointment from the API.

  3. 3

    Match the client

    Look the client up in the other system by email or phone before creating anyone, so repeat clients don't turn into duplicates.

  4. 4

    Write it, and log the result

    Create or update the record, and keep a log of what was written. When something fails, someone can see which booking and why.

Questions people ask

Does Acuity Scheduling have webhooks?

It does, for appointments being scheduled, rescheduled, canceled or changed, and for completed orders. You can set them in the account or create them through the API, and each one tells your server which appointment changed.

Does Acuity Scheduling integrate with Zoom?

Natively. Connect Zoom in Acuity and each video appointment gets its own meeting link, sent to both you and the client, with no API work.

Does Acuity Scheduling work with Zapier?

There's an official Acuity Scheduling app on Zapier with triggers such as a new or canceled appointment. For a single step into another tool, it's usually quicker than the API.

Do I need a developer to use the Acuity Scheduling API?

For direct API or webhook work, generally yes: someone has to write, host and maintain the code. n-frames builds and runs those Acuity connections for appointment businesses, from the listener to the record it updates.

Which Acuity plan includes API access?

Premium, the plan Acuity used to call Powerhouse. Confirm on the account itself before building, since plan contents can change.

Let's talk

Tell us the one thing your team does manually that eats up time. We read every message and reply within a day.