Acuity Scheduling API

Name: Acuity Scheduling API
Brand: Acuity Scheduling API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentProductivityCalendar Schedulingbasic33 EndpointsREST

For Agents

Book, cancel, and reschedule appointments and check availability through Acuity Scheduling's API.

Install Jentic One Beta

Connect the Acuity Scheduling API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Acuity Scheduling API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with Acuity Scheduling API.

Book and look up appointments via /appointments and /appointments/{id}

Cancel or reschedule appointments through /appointments/{id}/cancel and /appointments/{id}/reschedule

Check open availability across calendars with /availability/dates, /availability/times, and /availability/check-times

GET STARTED

Start building with Acuity Scheduling API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use Acuity Scheduling API for, with concrete tasks.

★ AI-driven appointment booking

Service businesses (clinics, coaches, salons) want chat or voice agents to book appointments without a human dispatcher. An agent calls /availability/dates and /availability/times for the chosen appointment type, picks a slot, and POSTs to /appointments with client details. Acuity handles the calendar collision checks and confirmation email automatically.

Get available times for appointment type 123 on 2026-06-12 from /availability/times, then POST to /appointments with chosen time and client details

Cancellation and reschedule self-service

Customers cancel or reschedule via email, SMS, or chat. An agent looks up the appointment by id, calls /appointments/{id}/cancel or /appointments/{id}/reschedule with a new datetime, and confirms the change to the customer. This avoids the manual reschedule loop that typically eats receptionist time.

Call POST /appointments/456/reschedule with the new datetime and notify the client via the existing channel

Calendar block-off automation

Owners block staff calendars when team members are off, training, or in internal meetings. An agent can POST to /blocks with the calendar id and time range to prevent new bookings during that window, and remove the block when the period ends. This avoids double-booking when staff schedules change last minute.

POST a block to /blocks for calendar 7 covering 2026-06-15 14:00-18:00 with reason 'team training'

AI agent integration

Service businesses building agent assistants expose Acuity through Jentic alongside payment and SMS APIs. Through Jentic, basic auth credentials live in the vault, and the agent searches by intent - e.g. 'book an Acuity appointment' - without juggling raw user IDs and API keys.

Search Jentic for 'book an Acuity appointment', load the schema, and execute it with appointment_type, datetime, and client info

Key Endpoints

33 endpoints — jentic publishes the only available openapi specification for acuity scheduling api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

GET

/appointments

List appointments

POST

/appointments

Book an appointment

POST

/appointments/{id}/cancel

Cancel an appointment

POST

/appointments/{id}/reschedule

Reschedule an appointment

GET

/availability/times

Get available times

GET

/availability/dates

Get available dates

GET

/clients

List clients

POST

/blocks

Block calendar time

GET

/appointments

List appointments

POST

/appointments

Book an appointment

POST

/appointments/{id}/cancel

Cancel an appointment

POST

/appointments/{id}/reschedule

Reschedule an appointment

GET

/availability/times

Get available times

GET

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Your Acuity User ID and API key are stored once, encrypted, by your own Jentic One instance and injected as the Basic auth header at execution time. They never enter the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'book an Acuity appointment' or 'check availability', and Jentic returns the matching operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

Time to first call

FAQs

Specific to using Acuity Scheduling API through Jentic.

Why is there no official OpenAPI spec for Acuity Scheduling API?

Acuity Scheduling does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Acuity Scheduling API via structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer.

What authentication does the Acuity Scheduling API use?

Acuity uses HTTP basic auth with a User ID as username and an API key as password, both available in the Acuity Integrations settings. Through Jentic, the credential pair is stored encrypted in your Jentic One instance and never appears in the agent's prompt context.

Can I book and reschedule appointments with the Acuity Scheduling API?

Yes. POST /appointments creates a booking with appointment_type_id, datetime, and client fields. POST /appointments/{id}/cancel and POST /appointments/{id}/reschedule handle the cancellation and reschedule paths, with Acuity sending confirmation emails to the client automatically.

What are the rate limits for the Acuity Scheduling API?

The OpenAPI spec does not declare explicit rate limits, so check Acuity's developer docs for the current ceiling. Use availability endpoints (/availability/times, /availability/check-times) before posting a booking to reduce 409-style collision retries.

How do I check availability and book through Jentic?

Run pip install jentic, search Jentic for 'check Acuity availability', load GET /availability/times, then chain a search for 'book an Acuity appointment' to load POST /appointments. Jentic injects basic auth from the vault, so the agent only supplies appointment_type_id, datetime, and client details.

Does the Acuity Scheduling API support intake forms?

Yes. The /forms endpoint lists the intake forms configured in the account, and form answers are returned alongside an appointment record. That lets an agent pull a client's intake responses at the same time it confirms the booking.

Can I limit what my agent is allowed to do with the Acuity Scheduling API?

Yes. Jentic One is self-hosted, so your own rules decide which Acuity operations and credentials the agent may use. Because Acuity puts the appointment id in the URL path (/appointments/{id}/reschedule, /appointments/{id}/cancel), you can pin the agent to a single appointment and to a single action, for example allowing it to reschedule that booking while cancelling and creating blocks on /blocks stay off. Only the operations you explicitly allow are callable, and the User ID and API key are injected at execution time rather than exposed to the agent.

Acuity Scheduling API

Connect the Acuity Scheduling API to your agent

Capabilities

Start building with Acuity Scheduling API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs