[Cotlet](https://cotlet.dev/index.md) · [Integrations](https://cotlet.dev/integrations.md) · [How it works](https://cotlet.dev/how-it-works.md) · [Use cases](https://cotlet.dev/use-cases.md) · [Security](https://cotlet.dev/security.md) · [For developers](https://cotlet.dev/for-developers.md) · [For automation agencies](https://cotlet.dev/for-agencies.md) · [Blog](https://cotlet.dev/blog.md) · [API docs](https://cotlet.dev/docs.md) · [Help center](https://cotlet.dev/help.md) · [Changelog](https://cotlet.dev/changelog.md) · [Contact](https://cotlet.dev/contact.md) · [Pricing](https://cotlet.dev/pricing.md) · [Sign up](https://cotlet.dev/signup)

# Acuity Scheduling API and MCP server

> Acuity Scheduling has a full REST API but no official MCP server (checked 17 Oct 2026). The API uses HTTP Basic auth with your user ID and API key, and Acuity says API access is available on the Premium plan (formerly Powerhouse), so Starter and Standard accounts have no key to give an agent.

Online scheduling software for service businesses: clients book appointment types on your scheduler, and you manage calendars, availability, blocked time and the client list in the Acuity admin.

## What is the Acuity Scheduling API?

Cotlet's Acuity Scheduling API exposes 10 endpoints for your own Acuity Scheduling account: list appointments, get appointment, list appointment types, check availability dates, check availability times, book appointment, reschedule appointment, cancel appointment, update appointment and block off time. The list_appointments endpoint returns appointments with client, type, calendar, time and payment status, filtered by date, calendar, type or client. Each endpoint takes simple JSON inputs like calendar_id, appointment_type_id or appointment_id and works both as an operation of the acuity_scheduling_read or acuity_scheduling_write MCP tool for agents and as a REST call for scripts.

- **Category:** [Local services & SaaS](https://cotlet.dev/integrations/category/local-services-saas.md)
- **Endpoints:** 10 (5 read, 5 write)
- **Updated:** 2026-10-20

Acuity Scheduling has a full REST API but no official MCP server (checked 17 Oct 2026). Cotlet is a hosted MCP server and REST API for Acuity Scheduling with 10 endpoints (5 read, 5 write): you sign in once in your own cloud browser, your AI agent does the work.

## Does Acuity Scheduling have an official API?

Acuity Scheduling has a full REST API but no official MCP server (checked 17 Oct 2026). The API uses HTTP Basic auth with your user ID and API key, and Acuity says API access is available on the Premium plan (formerly Powerhouse), so Starter and Standard accounts have no key to give an agent.

| Task | Acuity Scheduling official | Cotlet |
|---|---|---|
| List and filter appointments | Yes: GET /appointments, Premium plan | Yes |
| Check open dates and times for an appointment type | Yes: GET /availability/dates and /availability/times, Premium plan | Yes |
| Book an appointment for a client | Yes: POST /appointments, Premium plan | Yes |
| Reschedule an appointment | Yes: PUT /appointments/{id}/reschedule, Premium plan; the admin flag skips availability checks | Yes |
| Cancel an appointment or mark a no-show | Yes: PUT /appointments/{id}/cancel, Premium plan; a cancellation cannot be undone | Yes |
| Edit client details, notes and label on an appointment | Yes: PUT /appointments/{id}, only a white-list of fields, Premium plan | Yes |
| Block off time on a calendar | Yes: POST /blocks, Premium plan | Yes |
| List appointment types and calendars | Partly: Their reference pages did not open when we checked, so the endpoints are not confirmed here | Yes |

Sources: [Acuity developers: Quick Start](https://developers.acuityscheduling.com/reference/quick-start), [Acuity developers: GET /appointments](https://developers.acuityscheduling.com/reference/get-appointments), [Acuity Help: Using custom CSS, webhooks, and APIs](https://help.acuityscheduling.com/hc/en-us/articles/16676949253389-Using-custom-CSS-webhooks-and-APIs), [Acuity developers: Documentation index for LLMs](https://developers.acuityscheduling.com/llms.txt)

## For AI agents

```text
Acuity Scheduling has a full REST API but no official MCP server (checked 17 Oct 2026). The API uses HTTP Basic auth with your user ID and API key, and Acuity says API access is available on the Premium plan (formerly Powerhouse), so Starter and Standard accounts have no key to give an agent.
Cotlet provides a hosted MCP server and REST API for Acuity Scheduling: 10 tools (5 read, 5 write).
Access       Sign up at https://cotlet.dev/app/signup?app=acuity-scheduling, then request the app and create API keys in the Cotlet console.

MCP server   https://cotlet.dev/mcp/v1
MCP tools    acuity_scheduling_read, acuity_scheduling_write, reads and writes apart; call one with {"operation": "<operation>", "arguments": {...}}
REST base    https://cotlet.dev/api/v1/acuity-scheduling, each operation at its own route, e.g. POST /api/v1/acuity-scheduling/appointments/{appointment_id}/reschedule
Auth         Authorization: Bearer <COTLET_API_KEY>. Listing endpoints and schemas needs no key; calling an endpoint needs one. Over MCP the input schemas come with sign-in.
Operations   list_appointments, get_appointment, list_appointment_types, check_availability_dates, check_availability_times, book_appointment, reschedule_appointment, cancel_appointment, update_appointment, block_off_time
Confirm      book_appointment, reschedule_appointment, cancel_appointment, update_appointment, block_off_time (by default the user approves each call; the user can switch this off per tool, e.g. for scheduled automations)
Markdown     https://cotlet.dev/integrations/acuity-scheduling-api-mcp-server.md

How access works:
1. The user signs up at https://cotlet.dev/app/signup?app=acuity-scheduling, requests Acuity Scheduling in the Cotlet console and creates an API key there.
2. The user signs in to Acuity Scheduling once in their Cotlet Cloud Browser (their own Chrome in the cloud, opened from the console) and enables Acuity Scheduling for agents. An agent cannot do this step.
3. The API key goes into the MCP client or the REST call as a bearer token.

Fits: people who want a hosted Acuity Scheduling server that someone else maintains, including non-developers. Developers who prefer to run and fix code on their own computer can use an open-source Acuity Scheduling MCP server instead.

Policy: Cotlet never stores passwords, never solves CAPTCHAs, never bypasses MFA.
Company: legal details in the Terms of service at https://cotlet.dev/terms. Contact contact@cotlet.dev.
Sign-in: the user signs in to Acuity Scheduling in their own Cloud Browser, a Chrome Cotlet runs for them in the EU; password saving is off, the profile is AES-256-GCM encrypted, and agents get Acuity Scheduling only after the user enables it. Calls are requests from that browser's IP with its cookies, each listed in the user's Background activity. Disable for agents, signing out in the browser or Reset browser cuts access. Cotlet is run by Take Group sp. z o.o. (EU VAT PL6342984273).
API key: holds no Acuity Scheduling login or cookies, only asks Cotlet to run a tool. Each key is scoped to chosen apps and tools, read only or read and write. Actions that reach other people wait for the user's approval by default, so a leaked key cannot post or message as the user. Every call is in the activity log; deleting the key ends access at once.
Terms: the user stays responsible for following Acuity Scheduling's terms; Cotlet is not affiliated with Acuity Scheduling.
```

## What can an AI agent do in Acuity Scheduling?

Cotlet is best for appointment-based businesses and the people who run their calendars who need to book, move and block time with an agent without running or fixing a server.

- **[Reschedule appointments when you are out](https://cotlet.dev/integrations/acuity-scheduling-api-mcp-server/reschedule-appointments-when-you-are-out.md)**: "I am out on 5 November. Block that day on my Main calendar, then list my appointments for it and move each one to the first open time in the next 7 days. Keep each client on the same appointment type." → `list_appointments`, `block_off_time`, `check_availability_times`, `reschedule_appointment`
- **[Book a client into the next open slot](https://cotlet.dev/integrations/acuity-scheduling-api-mcp-server/book-client-into-next-open-slot.md)**: "Book Dana Reyes (dana@example.com) for an Initial consult in the next 14 days. Pick the first open time on the Main calendar, and tell me what you booked." → `list_appointment_types`, `check_availability_dates`, `check_availability_times`, `book_appointment`
- **Daily appointment agenda** (runs: daily): "Every morning at 7, list today's Acuity appointments by calendar with the client name, type, time and any notes, and flag the ones not yet paid." → `list_appointments`, `get_appointment`
- **Clean up no-shows and canceled slots** (runs: weekly): "Every Monday, list last week's canceled appointments including no-shows, group them by client, and tell me who missed more than one." → `list_appointments`
- **Add intake notes to appointments**: "For tomorrow's appointments, add the note "Bring last report" to every Follow-up and tell me which ones I changed." → `list_appointments`, `update_appointment`

## Can Acuity Scheduling automations run on a schedule in n8n, Make or Zapier?

Yes. Cotlet does not replace your automation platform: it gives it a Acuity Scheduling connection it does not have, with the same API key as your agent. Write actions ask for your OK by default; switch that off in your dashboard for the tools you choose, for example to daily appointment agenda, and the schedule runs on its own. Cotlet runs in the cloud, so it keeps going while your computer is off.

| Where | How to connect | How to schedule |
|---|---|---|
| Your AI agent | Add https://cotlet.dev/mcp/v1 with your API key. | A scheduled agent run, for example a Claude Code routine. |
| n8n | MCP Client node with https://cotlet.dev/mcp/v1, or an HTTP Request node with the endpoint's method and URL, such as GET https://cotlet.dev/api/v1/acuity-scheduling/appointments. | Schedule Trigger node. |
| Make | HTTP module: the endpoint's method and URL with an Authorization: Bearer header, and a JSON body for POST, PUT and PATCH. | Scenario schedule. |
| Zapier | Webhooks by Zapier, Custom Request: the same method, URL, header and body. | Schedule by Zapier trigger. |
| Your own script | GET https://cotlet.dev/api/v1/acuity-scheduling/appointments with your API key. | cron or GitHub Actions. |

## Tools

**For AI agents:** Every endpoint and its schema is public. The 10 endpoints on this page, with parameters and example responses, can be listed without an account. Calling one returns 401 without an API key and 403 while the key has no access to Acuity Scheduling.

### list_appointments

Appointments with client, type, calendar, time and payment status, filtered by date, calendar, type or client. Access: read. REST: `GET /api/v1/acuity-scheduling/appointments`. MCP: `acuity_scheduling_read → list_appointments`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `min_date` | date | no | Only appointments on or after this date. |
| `max_date` | date | no | Only appointments on or before this date. |
| `calendar_id` | integer | no | Only this calendar. |
| `appointment_type_id` | integer | no | Only this appointment type. |
| `email` | string | no | Only this client's email. |
| `first_name` | string | no | Only this client's first name. |
| `last_name` | string | no | Only this client's last name. |
| `canceled` | boolean | no | true returns canceled appointments instead of scheduled ones. Default: false. |
| `include_canceled` | boolean | no | true returns scheduled and canceled together. Default: false. |
| `direction` | enum | no | DESC or ASC by date. Default: DESC. |
| `exclude_forms` | boolean | no | true leaves intake forms out. Default: false. |
| `max` | integer | no | Most appointments to return. Default: 100. |

Returns appointments newest first by default; set direction to ASC for oldest first. Canceled appointments are left out unless canceled is true or include_canceled is true. Canceled results include noShow, true when an admin marked the appointment as a no-show. Without max, Acuity returns 100. Each item carries paid, amountPaid and the intake form answers; set exclude_forms to leave the forms out and answer faster.

Example response:

```json
{
  "appointments": [
    {
      "appointment_id": 1840211,
      "first_name": "Ana",
      "last_name": "Lopez",
      "email": "ana@example.com",
      "type": "Initial consult",
      "appointment_type_id": 5120043,
      "calendar": "Main",
      "calendar_id": 27238,
      "datetime": "2026-11-05T09:30:00-0500",
      "end_time": "10:30am",
      "duration": 60,
      "price": "90.00",
      "paid": "no",
      "can_client_cancel": true,
      "can_client_reschedule": true
    }
  ]
}
```

### get_appointment

One appointment with its intake form answers, notes, label and payment fields. Access: read. REST: `GET /api/v1/acuity-scheduling/appointments/{appointment_id}`. MCP: `acuity_scheduling_read → get_appointment`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `appointment_id` | integer | yes | Appointment ID from list_appointments. |

Returns one appointment by ID, with the answers to your intake forms, the notes, the label, and the paid and amountPaid fields. It also returns the confirmation page link and whether the client can cancel or reschedule. Use it before an edit to read what is there now.

Example response:

```json
{
  "appointment_id": 1840211,
  "first_name": "Ana",
  "last_name": "Lopez",
  "email": "ana@example.com",
  "phone": "+15555550142",
  "type": "Initial consult",
  "calendar": "Main",
  "datetime": "2026-11-05T09:30:00-0500",
  "duration": 60,
  "price": "90.00",
  "paid": "no",
  "amount_paid": "0.00",
  "notes": "",
  "label": null,
  "forms": [
    {
      "name": "Intake",
      "values": [
        {
          "name": "Reason for visit",
          "value": "Back pain"
        }
      ]
    }
  ],
  "confirmation_page": "https://acuityscheduling.com/schedule.php?owner=11111111&action=appt&id%5B%5D=abc123"
}
```

### list_appointment_types

Your appointment types with duration, price and the calendars that offer each one. Access: read. REST: `GET /api/v1/acuity-scheduling/appointment-types`. MCP: `acuity_scheduling_read → list_appointment_types`.

No parameters.

Returns the appointment types you offer, each with its ID, name, duration, price and the calendars that offer it. Use the IDs in the availability and booking calls.

Example response:

```json
{
  "appointment_types": [
    {
      "appointment_type_id": 5120043,
      "name": "Initial consult",
      "duration": 60,
      "price": "90.00",
      "calendars": [
        {
          "calendar_id": 27238,
          "name": "Main"
        }
      ]
    },
    {
      "appointment_type_id": 5120051,
      "name": "Follow-up",
      "duration": 30,
      "price": "45.00",
      "calendars": [
        {
          "calendar_id": 27238,
          "name": "Main"
        },
        {
          "calendar_id": 27240,
          "name": "Room 2"
        }
      ]
    }
  ]
}
```

### check_availability_dates

Days in one month that have openings for an appointment type. Access: read. REST: `GET /api/v1/acuity-scheduling/appointment-types/{appointment_type_id}/availability-dates/check`. MCP: `acuity_scheduling_read → check_availability_dates`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `appointment_type_id` | integer | yes | Appointment type ID from list_appointment_types. |
| `month` | string | yes | Month to check, e.g. '2026-11'. |
| `calendar_id` | integer | no | Calendar ID from list_appointment_types or list_appointments. Without it, every calendar that offers the type is checked. |
| `addon_ids` | integer[] | no | Add-ons of this appointment type to include. |
| `timezone` | string | no | Long-form timezone ID, e.g. 'America/New_York'. |

Returns the dates in the month that have at least one open time for the appointment type, matching what clients see on your scheduler. Pass add-ons that belong to the type, because they change the openings. Call check_availability_times for the actual times on one of these dates.

Example response:

```json
{
  "dates": [
    "2026-11-03",
    "2026-11-04",
    "2026-11-05",
    "2026-11-09"
  ]
}
```

### check_availability_times

Open times on one date for an appointment type. Access: read. REST: `GET /api/v1/acuity-scheduling/appointment-types/{appointment_type_id}/availability-times/check`. MCP: `acuity_scheduling_read → check_availability_times`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `appointment_type_id` | integer | yes | Appointment type ID from list_appointment_types. |
| `date` | string | yes | Day to check, e.g. '2026-11-03'. |
| `calendar_id` | integer | no | Calendar ID from list_appointment_types or list_appointments. Without it, every calendar that offers the type is checked. |
| `addon_ids` | integer[] | no | Add-ons of this appointment type to include. |
| `timezone` | string | no | Long-form timezone ID, e.g. 'America/New_York'. |
| `ignore_appointment_ids` | integer[] | no | Appointments to ignore, so their own slots show as open. Use when rescheduling. |

Returns the open start times on one date for the appointment type, as ISO timestamps with offset, matching what clients see on your scheduler. To move an appointment to a time that overlaps its own slot, pass its ID in ignore_appointment_ids so the current slot counts as free.

Example response:

```json
{
  "times": [
    {
      "time": "2026-11-03T10:00:00-0500"
    },
    {
      "time": "2026-11-03T11:00:00-0500"
    },
    {
      "time": "2026-11-03T14:00:00-0500"
    }
  ]
}
```

### book_appointment

Book a client into an open time for an appointment type. Access: write, asks the user first. REST: `POST /api/v1/acuity-scheduling/appointment-types/{appointment_type_id}/appointments`. MCP: `acuity_scheduling_write → book_appointment`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `appointment_type_id` | integer | yes | Appointment type ID from list_appointment_types. |
| `datetime` | string | yes | Start time from check_availability_times, e.g. '2026-11-03T10:00:00-0500'. |
| `first_name` | string | yes | Client first name. |
| `last_name` | string | yes | Client last name. |
| `email` | string | no | Client email. |
| `phone` | string | no | Client phone. |
| `calendar_id` | integer | no | Calendar ID from list_appointment_types or list_appointments. Without it, every calendar that offers the type is checked. |
| `timezone` | string | no | Long-form timezone ID, e.g. 'America/New_York'. |

Creates an appointment for the client at the datetime you pass, for the appointment type and calendar. Pass a time returned by check_availability_times. The client needs a first and last name (Acuity requires both for a client profile). Returns the new appointment with its ID and confirmation link. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "appointment_id": 1841502,
  "first_name": "Dana",
  "last_name": "Reyes",
  "email": "dana@example.com",
  "type": "Initial consult",
  "calendar": "Main",
  "datetime": "2026-11-03T10:00:00-0500",
  "duration": 60,
  "price": "90.00",
  "paid": "no",
  "confirmation_page": "https://acuityscheduling.com/schedule.php?owner=11111111&action=appt&id%5B%5D=def456"
}
```

### reschedule_appointment

Move an appointment to a new date and time, or to another calendar. Access: write, asks the user first. REST: `POST /api/v1/acuity-scheduling/appointments/{appointment_id}/reschedule`. MCP: `acuity_scheduling_write → reschedule_appointment`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `appointment_id` | integer | yes | Appointment ID from list_appointments. |
| `datetime` | string | yes | New start time, e.g. '2026-11-06T09:30:00-0500'. |
| `calendar_id` | integer | no | Move to this calendar. Without it, the calendar stays. |
| `send_notification` | boolean | no | false sends no email or text to the client. Default: true. |

Moves one appointment to the new datetime, and to another calendar if you pass one. Acuity returns an error if the appointment is canceled, is a class series, or the new time is not an open slot. Acuity emails and texts the client about the new time unless send_notification is false. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "appointment_id": 1840211,
  "first_name": "Ana",
  "last_name": "Lopez",
  "type": "Initial consult",
  "calendar": "Main",
  "datetime": "2026-11-06T09:30:00-0500",
  "duration": 60,
  "notified_client": true
}
```

### cancel_appointment

Cancel an appointment, optionally marking a no-show. Access: write, asks the user first. REST: `POST /api/v1/acuity-scheduling/appointments/{appointment_id}/cancel`. MCP: `acuity_scheduling_write → cancel_appointment`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `appointment_id` | integer | yes | Appointment ID from list_appointments. |
| `cancel_note` | string | no | Text included in the cancellation message to the client. |
| `mark_no_show` | boolean | no | true records a no-show. Default: false. |
| `send_notification` | boolean | no | false sends no email or text. Default: true. |

Cancels one appointment. A cancellation cannot be undone, but the appointment stays viewable. Pass a note to include it in the cancellation message, and mark_no_show to record that the client did not come. Acuity emails and texts the client unless send_notification is false. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "appointment_id": 1840299,
  "first_name": "Marc",
  "last_name": "Dubois",
  "type": "Annual review",
  "datetime": "2026-11-05T14:00:00-0500",
  "canceled": true,
  "no_show": false,
  "notified_client": true
}
```

### update_appointment

Edit client name, phone, email, notes or label on an appointment. Access: write, asks the user first. REST: `PATCH /api/v1/acuity-scheduling/appointments/{appointment_id}`. MCP: `acuity_scheduling_write → update_appointment`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `appointment_id` | integer | yes | Appointment ID from list_appointments. |
| `first_name` | string | no | New first name. Cannot be empty. |
| `last_name` | string | no | New last name. Cannot be empty. |
| `phone` | string | no | New phone. |
| `email` | string | no | New email. |
| `notes` | string | no | Replaces the appointment notes. |
| `label` | string | no | Label name. An appointment holds one label. |

Changes the fields you pass on one appointment and leaves the rest. Only these can change: first and last name (never blank), phone, email, notes, one label, and intake form fields. It does not move or cancel the booking. Use reschedule_appointment or cancel_appointment for that. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "appointment_id": 1840211,
  "first_name": "Ana",
  "last_name": "Lopez",
  "notes": "Bring last report",
  "label": "Returning",
  "datetime": "2026-11-05T09:30:00-0500"
}
```

### block_off_time

Block a time range on a calendar so no new client can book it. Access: write, asks the user first. REST: `POST /api/v1/acuity-scheduling/calendars/{calendar_id}/off-time/block`. MCP: `acuity_scheduling_write → block_off_time`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `calendar_id` | integer | yes | Calendar to block. |
| `start` | string | yes | Start of the block, e.g. '2026-11-05T09:00:00-0500'. |
| `end` | string | yes | End of the block, e.g. '2026-11-05T17:00:00-0500'. |
| `notes` | string | no | Note for yourself on the block. |

Adds a time block on one calendar, with optional notes. It stops new bookings in that range, but an appointment already there stays on the calendar, and group classes are not affected. Returns the block ID and a readable description of the range. Remove a block in Acuity under Availability, Edit Availability/Limits, Blocked Time. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "block_id": 7790112,
  "notes": "Out sick",
  "description": "Thursday 5 November 2026 9:00am - 5:00pm"
}
```

## How do I connect Acuity Scheduling to Claude Code, Codex or Cursor?

Connecting Acuity Scheduling takes three steps: sign up, sign in to Acuity Scheduling once in your Cloud Browser and enable it for agents, then add one MCP server or call the REST API with the same key.

### Connect Acuity Scheduling to your agent.

1. **Create an account** Sign up and add Acuity Scheduling in the console. Your API key is there too.

2. **Sign in to Acuity Scheduling in your Cloud Browser** Open your Cloud Browser in the console: your own Chrome in the cloud. Sign in to Acuity Scheduling there yourself, the way you always do, then press Enable for agents, read only or read and write. We never save your password, and your agent keeps working even when your computer is off.

3. **Add Cotlet to your agent** Paste the snippet for your client. The same server and key serve every app you connect, so you do this once.

   Claude Code:

```
claude mcp add --transport http cotlet \
  https://cotlet.dev/mcp/v1 \
  --header "Authorization: Bearer $COTLET_API_KEY"
```

   Cursor:

```
{
  "mcpServers": {
    "cotlet": {
      "url": "https://cotlet.dev/mcp/v1",
      "headers": {
        "Authorization": "Bearer ${COTLET_API_KEY}"
      }
    }
  }
}
```

   Codex:

```
# ~/.codex/config.toml
[mcp_servers.cotlet]
url = "https://cotlet.dev/mcp/v1"
bearer_token_env_var = "COTLET_API_KEY"
```

4. **Ask your agent** Ask in plain words. Your agent finds the Acuity Scheduling tools on the server and calls them for you; anything that reaches other people waits for your OK unless you switch that off for a tool.

```
I am out on 5 November. Block that day on my Main calendar, then list my appointments for it and move each one to the first open time in the next 7 days. Keep each client on the same appointment type.
```

### Call Acuity Scheduling from your scripts.

1. **Export your API key** Your scripts use the same API key as your agent. Keep it in an environment variable, never in your code.

```
export COTLET_API_KEY="cotlet_..."
```

2. **Call a tool** Every tool is an endpoint under /api/v1/acuity-scheduling with its own method and path, listed with the endpoints above. Path parameters go in the URL; the other parameters go in the query for GET and DELETE and in a JSON body otherwise.

```
curl -X POST https://cotlet.dev/api/v1/acuity-scheduling/appointments/1840211/reschedule \
  -H "Authorization: Bearer $COTLET_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"datetime":"2026-11-06T09:30:00-0500","send_notification":true}'
```

3. **Read the result** You get plain JSON back, ready for your script. A failed call costs nothing.

```
{
  "appointment_id": 1840211,
  "first_name": "Ana",
  "last_name": "Lopez",
  "type": "Initial consult",
  "calendar": "Main",
  "datetime": "2026-11-06T09:30:00-0500",
  "duration": 60,
  "notified_client": true
}
```

## Why use Cotlet for Acuity Scheduling?

**Built for agents**

- One MCP server for every app you connect.
- The same tools as a REST API for scripts and cron jobs.
- Works with Claude Code, Codex and Cursor.

**Your login stays yours**

- You sign in to Acuity Scheduling yourself, in your own Cloud Browser. We never save your password; the profile is encrypted with AES-256-GCM, the cipher 1Password uses.
- A+ on Qualys SSL Labs, securityheaders.com and Mozilla Observatory.
- The model never sees a login.
- No stored passwords, no CAPTCHA solving, no MFA bypass.

**You stay in control**

- Scope each API key: its apps, its tools, read only or read and write.
- Anything that reaches other people waits for your OK, so a leaked key cannot post or message as you.
- Every background request listed in your Background activity. Disable for agents in one click.

**Kept working for you**

- We test every integration every 6 hours.
- When Acuity Scheduling changes, the tool pauses until we fix it.
- Failed calls cost nothing.

## Is it safe to connect Acuity Scheduling to Cotlet?

Yes. You sign in to Acuity Scheduling yourself, in your own Cloud Browser, and we never save your password. Your agents only get Acuity Scheduling once you enable it, and every background request is listed. The browser profile is stored encrypted with AES-256-GCM, the same cipher 1Password uses for its vaults and Apple for iCloud Keychain. Independent public scanners grade cotlet.dev A+ and find it clean; click a result to rerun it yourself.

- **A+ on Qualys SSL Labs**: Encryption in transit: TLS setup and certificates, on all four server addresses. [Live result](https://www.ssllabs.com/ssltest/analyze.html?d=cotlet.dev)
- **A+ on securityheaders.com**: Browser protections sent with every page, all six headers present. [Live result](https://securityheaders.com/?q=cotlet.dev&followRedirects=on)
- **A+ on Mozilla Observatory**: Mozilla's web security baseline: score 120 of 100, 12 of 12 tests passed. [Live result](https://developer.mozilla.org/en-US/observatory/analyze?host=cotlet.dev)
- **Clean on Sucuri SiteCheck**: No malware, spam or defacement, and not on any of 9 blocklists, Google Safe Browsing included. [Live result](https://sitecheck.sucuri.net/results/cotlet.dev)

[How Cotlet protects your access](https://cotlet.dev/security.md)

### Common concerns

**Who runs Cotlet?**

Cotlet is run by Take Group, a Polish software company working since 2019. Take Group runs about 3,200 websites on its own systems and has its own DevOps team for infrastructure security. We built and used integrations like this inside the company for years before opening them as Cotlet.

**Is this an official Acuity Scheduling integration?**

No, Cotlet is independent of Acuity Scheduling. Acuity Scheduling's own API is too limited for this work. Cotlet works through your own Acuity Scheduling account, the way you use Acuity Scheduling in the browser, so you need no partner approval and no developer setup.

**What about client data and GDPR?**

Cotlet is run from the EU and follows the GDPR. Cloud Browsers run in Finland, a Tier 1 country in the ITU Global Cybersecurity Index 2024. Data passes through a call and is not kept after it.

**Can I start with read only?**

Yes. Enable the app for agents as read only, or make the API key read only, and anything that reaches other people waits for your OK unless you switch that off per tool.

**Is it reliable?**

Every Cotlet service is checked every 3 minutes from Europe, North America, Asia and Australia. The live results and any outage are public at status.cotlet.dev.

**How do I stop?**

Press Disable for agents next to Acuity Scheduling in your console: your agents lose access at once and you stay signed in. Signing out of Acuity Scheduling in the browser works too, and Reset browser deletes the whole profile.

## Is there a Acuity Scheduling MCP server on GitHub?

Yes. Community Acuity MCP servers exist on GitHub, usually maintained by one person. You install one yourself, give it your Acuity user ID and API key, and fix it when something changes. That key needs the Premium plan. Cotlet hosts the same kind of server for you, signs in as you in the Acuity web app, and our team keeps it working.

|  | GitHub MCP server | Cotlet |
|---|---|---|
| Setup | Clone the repo, find your user ID and API key in Acuity, store them, add the server to each MCP client | Sign up, sign in to Acuity once, add one MCP server or API key |
| Plan needed | Premium, because the API key comes with it | Works in the Acuity web app you sign in to, no API key to find or store |
| When Acuity changes | It breaks until you or the maintainer fix it | Our team tests it daily and fixes it for you; failed calls are free |
| Your Acuity access | API key in a file on your computer, readable by any program you run | Signed in inside your own Cloud Browser in the EU, profile encrypted, only for the apps you enable, disabled for agents in one click |
| When access expires | Tools fail until you replace the key or fix the config by hand | Your Cloud Browser keeps you signed in; if Acuity logs you out, your agent gets a link to sign in again |
| Upkeep | You update, monitor and debug it yourself | Nothing to host or update |
| Where it runs | Your computer, while it is on | Hosted: Claude Code, Codex, Cursor, n8n and scripts, also on a schedule |
| Price | Free, paid for with your time | Free 7-day trial, then pay-as-you-go credit packs, no subscription |

### Which one fits you

**Pick Cotlet if**

- you are not a developer, or you do not want to maintain a server
- you need it to keep working when Acuity Scheduling changes, without checking it yourself
- your agent or a script should run it on a schedule, also while your computer is off

**Pick an open-source server if**

- you are comfortable installing, updating and fixing it yourself
- you want your sign-in to stay on your own computer
- you only need it now and then, from one MCP client

## How much does the Acuity Scheduling API cost?

Free 7-day trial with 2,000 credits, no card needed. After that, the Acuity Scheduling API is pay as you go with no limit on apps: Credit packs from $29 for 5,000 credits, one-time, no subscription. A successful call uses 20 to 30 credits (25 for most tools, about $0.10 to $0.15), your Cloud Browser uses 50 credits a day while it has an app enabled for agents, however many apps that is, and an agent driving the browser itself uses 5 credits a minute. Credit packs stay valid for 12 months and stack, so unused credits carry over.

| Credits | Price, one time | Calls at 25 credits | Per 1,000 credits |
|---|---|---|---|
| 5,000 | $29 | 200 | $5.80 |
| 15,000 | $79 | 600 | $5.27 |
| 32,000 | $149 | 1,280 | $4.66 |
| 60,000 | $249 | 2,400 | $4.15 |

Only successful calls use credits; failed calls and timeouts cost nothing. At a balance of 0 calls pause, never a surprise charge. Authenticate with the `Authorization: Bearer` header. [See full pricing](https://cotlet.dev/pricing.md)

## How Cotlet holds your access

Cotlet hosts MCP servers and REST APIs for apps with no usable API. Your agent works in your own Acuity Scheduling account.

- **Company details:** Cotlet is run by Take Group sp. z o.o., a company registered in Poland. Its full address and registration numbers are in the Terms of service. [Terms of service](https://cotlet.dev/terms)
- **Your sign-in:** You sign in to Acuity Scheduling yourself, in your own Cloud Browser: a Chrome we run for you in the EU, one per app. We never save your password (password saving is off), the profile is stored encrypted with AES-256-GCM, and your agents get Acuity Scheduling only after you enable it. When Acuity Scheduling signs you out, your agent gives you a link to sign in again. [Security](https://cotlet.dev/security.md)
- **Revoking access:** Press Disable for agents next to Acuity Scheduling, sign out of Acuity Scheduling in your Cloud Browser, or reset the browser. Every background request is listed in your Background activity. Actions that reach other people wait for your OK unless you switch that off per tool.
- **What we never do:** Store passwords, solve CAPTCHAs or bypass MFA.
- **Acuity Scheduling's terms:** You use your own Acuity Scheduling account and stay responsible for following Acuity Scheduling's terms. Cotlet is independent and not affiliated with Acuity Scheduling. [Terms](https://cotlet.dev/terms)
- **Contact:** Questions about the company, security or an app: [contact@cotlet.dev](mailto:contact@cotlet.dev)

## Frequently asked questions

**How do I get access?**

Sign up free, open Acuity Scheduling in the console and press Request access. Then you create your API key and connect Acuity Scheduling there.

**Do I need to be technical?**

No. You sign in to Acuity Scheduling once in your Cloud Browser, a normal Chrome you open from the console, and paste one command into your agent, or one URL into n8n. Your agent can walk you through it. There is no server to install, update or fix.

**Is it safe to connect Acuity Scheduling to Cotlet?**

Yes. You sign in to Acuity Scheduling yourself, in your own Cloud Browser in the EU, and we never save your password. Your agents only get Acuity Scheduling once you enable it, every background request is listed, and the browser profile is stored encrypted with AES-256-GCM, the cipher 1Password uses for its vaults. The AI model never sees a login, posts and messages wait for your OK, and Disable for agents cuts access in one click. Independent scanners grade cotlet.dev A+ on Qualys SSL Labs, securityheaders.com and Mozilla Observatory; live results are on https://cotlet.dev/security.

**Is a hosted server safer than a local one? My Acuity Scheduling sign-in would leave my computer.**

On Cotlet you sign in inside your own Cloud Browser, which only you open, and its profile is stored encrypted with AES-256-GCM in the EU. Agents get only the apps you enable, and every background request is listed. A local server keeps your Acuity Scheduling cookie in a plain file on your computer, readable by any program you run, and stops when your computer is off.

**Why does Cotlet send requests instead of clicking in my browser?**

To be fast, Cotlet doesn't click through Acuity Scheduling's pages. It sends the same requests your browser would, from your browser's IP with its cookies, without opening a window. Acuity Scheduling sees the same browser and IP you signed in with, and every request is listed in your Background activity.

**What if someone gets my Cotlet API key?**

The key holds no Acuity Scheduling login or cookies, it only asks Cotlet to run a tool. It can call only the apps and tools you gave it, and a read-only key changes nothing. Anything that reaches other people, like posts, comments or messages, waits for your OK in the dashboard by default, so a leaked key cannot post or message as you. When you switch approval off for a scheduled job, give that job its own key limited to that one tool. Every call is in your activity log, and deleting the key ends access at once.

**Why a signed-in browser and not OAuth, like other integration platforms?**

Acuity Scheduling offers no OAuth token you can simply grant for these tools: its official API leaves them out or needs a developer app, a plan or an approval first (see the official API section above). That is why Cotlet sets the limits itself: per key, per tool, with your approval before anything reaches other people. Cotlet is run by Take Group sp. z o.o., an EU company (VAT PL6342984273).

**Which Acuity plan do I need?**

Acuity says API access and CSS customization are on the Premium plan (formerly Powerhouse), and webhooks are on any plan (checked 17 Oct 2026). Cotlet works through the Acuity web app you sign in to, not through the API key, so there is no key to find or store. Features your plan does not include stay unavailable to your agent too.

**Can my agent post or send messages in Acuity Scheduling without asking me?**

No. Every call to book_appointment, reschedule_appointment, cancel_appointment, update_appointment or block_off_time waits for your OK by default. For scheduled automations you can switch confirmation off per tool in your dashboard, for example only for approvals.

**Can I use the Acuity Scheduling API in n8n?**

Yes. Add https://cotlet.dev/mcp/v1 with your API key in n8n's MCP Client node, or call its endpoints under https://cotlet.dev/api/v1/acuity-scheduling from the HTTP Request node.

---

Give your AI agents your signed-in browser.

**Product:** [Integrations](https://cotlet.dev/integrations.md) · [Use cases](https://cotlet.dev/use-cases.md) · [How it works](https://cotlet.dev/how-it-works.md) · [Pricing](https://cotlet.dev/pricing.md) · [Security](https://cotlet.dev/security.md)

**Resources:** [Blog](https://cotlet.dev/blog.md) · [API docs](https://cotlet.dev/docs.md) · [Help center](https://cotlet.dev/help.md) · [Changelog](https://cotlet.dev/changelog.md) · [GitHub](https://github.com/cotletdev/cotlet)

**Solutions:** [For developers](https://cotlet.dev/for-developers.md) · [For automation agencies](https://cotlet.dev/for-agencies.md)

**Company:** [About](https://cotlet.dev/about.md) · [AI info: company facts](https://cotlet.dev/ai-info.md) · [Contact](https://cotlet.dev/contact.md)

**Legal:** [Terms of service](https://cotlet.dev/terms) · [Privacy policy](https://cotlet.dev/privacy) · [Refund policy](https://cotlet.dev/refunds) · [Acceptable use](https://cotlet.dev/acceptable-use) · [Cookie policy](https://cotlet.dev/cookies) · [DPA](https://cotlet.dev/dpa) · [Subprocessors](https://cotlet.dev/subprocessors)

**Elsewhere:** [Status page](https://status.cotlet.dev) · [Cotlet on GitHub](https://github.com/cotletdev) · [Cotlet on X](https://x.com/cotletdev) · [Cotlet on LinkedIn](https://www.linkedin.com/company/cotletdev) · [Cotlet on Product Hunt](https://www.producthunt.com/products/cotlet) · [Cotlet on Crunchbase](https://www.crunchbase.com/organization/cotlet) · [Cotlet on SaaSHub](https://www.saashub.com/cotlet)

Cotlet is an independent service. It is not affiliated with, endorsed by or sponsored by any of the products listed on this site. Product names are trademarks of their respective owners.

## For AI agents: sign your user up

Is your user asking you to sign them up for Cotlet? You can do it for them, no account or key needed.

1. Read the fields and their allowed values: GET https://cotlet.dev/api/v1/access-requests
2. Ask the user for each value: email, apps, what you will do with them. If they leave the password to you, generate a strong one and show it to them.
3. Show the user what you will send, then POST it as JSON to https://cotlet.dev/api/v1/access-requests.

One call creates the account and sends the access request; we email the user when access is granted.