canonical: https://jentic.com/apis/swaggerhub.k2anz/acuityscheduling

# K2anz Acuityscheduling

API for acuityscheduling.com. The API exposes 9 endpoints secured with basic authentication.

## For AI agents

Programmatically check_times, create. Covers 9 operations with basic authentication.

## Scope

Does not handle payments, communications, or crm - use for hr and recruiting only.

## Capabilities

- check_times
- create
- getAppointments
- dates
- GetAppointment
- get_appointment_types
- id

## Use cases

### HR and Recruiting Operations

Use the Acuityscheduling to perform hr recruiting operations programmatically. The API provides 9 endpoints covering core functionality including check_times, create, getappointments.

Example prompt: Call POST /availability/check-times to check_times

### Automated Appointments Management

Automate appointments operations by combining multiple Acuityscheduling endpoints. Agents can create and then getappointments in a single workflow.

Example prompt: Call POST /appointments to create, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call Acuityscheduling endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle basic tokens manually.

Example prompt: Search Jentic for 'check_times', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | /availability/check-times | check_times |
| POST | /appointments | create |
| GET | /appointments | getAppointments |
| GET | /availability/dates | dates |
| GET | /appointments/{id} | GetAppointment |
| GET | /appointment-types | get_appointment_types |
| GET | /appointments/{id}/cancel | id |
| PUT | /appointments/{id}/reschedule | reschedule |

## Key resources

- **Appointments** — Operations about Appointments
- **Availability** — Operations about Availability

## Why Jentic

- **Setup:** Wiring Acuityscheduling by hand means encoding HTTP basic auth against acuityscheduling.com/api/v1 and handling its scheduling flows yourself. Through Jentic you install once, import Acuityscheduling from the API Directory, store the basic credentials once, and your agent calls it.
- **Permission scoping:** Acuityscheduling puts the appointment id in the URL path (/appointments/{id}/...), so a rule can pin your agent to one appointment for reads, cancels, and reschedules. You choose the operations it may call, so cancelling or rescheduling is not included unless you add it, and it can stay limited to checking availability and reading appointments.
- **Credential handling:** Your Acuityscheduling basic credentials are stored once, encrypted, by your own Jentic One instance and injected at execution time. They never enter the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'check open appointment times' or 'book an appointment', and Jentic returns the matching Acuityscheduling operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Greenhouse** — Alternative hr recruiting API
- **Lever** — Alternative hr recruiting API
- **Workday** — Complementary hr recruiting API

## FAQ

### What authentication does the Acuityscheduling use?

The Acuityscheduling uses HTTP Basic authentication with username and password. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context.

### Can I check_times with the Acuityscheduling?

Yes. Use the POST /availability/check-times endpoint. The API returns structured JSON responses that agents can parse and act on directly.

### What are the rate limits for the Acuityscheduling?

Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.

### How do I check_times through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'check_times'. Jentic returns the matching Acuityscheduling operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the Acuityscheduling have?

The Acuityscheduling exposes 9 endpoints covering appointments, availability operations.

### 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 Scheduling operations and credentials the agent may use. You can keep it limited to reading appointments (GET /appointments, GET /appointments/{id}) and checking availability (GET /availability/dates, POST /availability/check-times), leaving out write actions like POST /appointments, cancel, and reschedule unless you add them. Because the appointment id lives in the URL path at /appointments/{id}, a rule can pin the agent to a single appointment for reads, cancels, and reschedules.