K2anz Acuityscheduling

Name: Acuityscheduling API
Brand: Acuityscheduling
Availability: InStock

★ Only Publicly Available OpenAPI DocumentHR recruitingRecruiting Atsbasic9 Endpoints

Install Jentic One Beta

Connect the Acuityscheduling to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Acuityscheduling, 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 Acuityscheduling API.

check_times

create

getAppointments

dates

GET STARTED

Start building with Acuityscheduling API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use Acuityscheduling API for, with concrete tasks.

★ 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.

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.

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.

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

Key Endpoints

9 endpoints — api for acuityscheduling.

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

PUT

/appointments/{id}/reschedule

reschedule

POST

/availability/check-times

check_times

POST

/appointments

create

GET

/appointments

getAppointments

GET

/availability/dates

dates

GET

/appointments/{id}

GetAppointment

GET

/appointment-types

Why Jentic?

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

Credential isolation

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.

Intent-based discovery

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.

Time to first call

FAQs

Specific to using Acuityscheduling API through Jentic.

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.

K2anz Acuityscheduling

Connect the Acuityscheduling to your agent

Capabilities

Start building with Acuityscheduling API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs