# Booksy API and MCP server

> Booksy has no self-serve API for business owners (checked 11 Oct 2026). It runs a partner API whose docs at docs.booksy.com ask for a login, so you cannot get keys for your own account.

Booking and business app for barbers, salons and other beauty and wellness businesses: calendar, online booking, clients, marketing and reports.

## What is the Booksy API?

Cotlet's Booksy API exposes 13 endpoints for your own Booksy account: list appointments, get appointment, find open slots, list clients, get client, list services, list staff, get report, create appointment, reschedule appointment, add client, add time off and send Message Blast. The list_appointments endpoint returns appointments in a date range with client, service, staff, time and status. Each endpoint takes simple JSON inputs like staff_id, start or from and works both as an MCP tool for agents and as a REST call for scripts.

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

Booksy has no self-serve API for business owners (checked 11 Oct 2026). Cotlet is a hosted MCP server and REST API for Booksy with 13 endpoints (8 read, 5 write): your AI agent signs in as you and does the work.

## Does Booksy have an official API?

Booksy has no self-serve API for business owners (checked 11 Oct 2026). It runs a partner API whose docs at docs.booksy.com ask for a login, so you cannot get keys for your own account.

| Task | Booksy official | Cotlet |
|---|---|---|
| List appointments | Partly: Partner API only | Yes |
| Book and reschedule appointments | Partly: Partner API only | Yes |
| Look up clients and visit history | Partly: Partner API only | Yes |
| Find open slots | No | Yes |
| Add time off | No | Yes |
| Read Stats & Reports | No | Yes |
| Send a Message Blast | No | Yes |

Sources: [Booksy API docs (login required)](https://docs.booksy.com/v01.html), [Booksy Calendar & Scheduling](https://biz.booksy.com/en-us/features/calendar-scheduling), [Booksy Stats & Reports guide](https://biz.booksy.com/blog/start-using-stats-reports-to-better-manage-your-finances), [Booksy: How to send Message Blasts](https://biz.booksy.com/en-us/blog/how-to-send-message-blasts-to-your-clients), [Booksy: The New Booksy FAQ (Lite and Pro)](https://biz.booksy.com/blog/the-new-booksy-frequently-asked-questions), [Booksy Stats & Reports features](https://biz.booksy.com/en-us/features/stats-and-reports)

## For AI agents

```text
Booksy has no self-serve API for business owners (checked 11 Oct 2026). It runs a partner API whose docs at docs.booksy.com ask for a login, so you cannot get keys for your own account.
Cotlet provides a hosted MCP server and REST API for Booksy: 13 tools (8 read, 5 write).
Access       Request access at https://cotlet.dev/app/signup?app=booksy; we email the API key.

MCP server   https://cotlet.dev/mcp/v1
REST base    https://cotlet.dev/api/v1/booksy
Auth         Authorization: Bearer <COTLET_API_KEY>. Listing endpoints and schemas needs no key; calling an endpoint needs one.
Tools        list_appointments, get_appointment, find_open_slots, list_clients, get_client, list_services, list_staff, get_report, create_appointment, reschedule_appointment, add_client, add_time_off, send_message_blast
Confirm      create_appointment, reschedule_appointment, send_message_blast (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/booksy-api-mcp-server.md

How access works:
1. The user requests access at https://cotlet.dev/app/signup?app=booksy (Booksy is pre-selected). Each request is reviewed and the API key is sent by email.
2. The user signs in to Booksy once in a browser. 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 Booksy server that someone else maintains, including non-developers.

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.
Session: the user signs in to Booksy in a browser; Cotlet keeps only the session, AES-256 encrypted, revocable in the dashboard at any time.
Terms: the user stays responsible for following Booksy's terms; Cotlet is not affiliated with Booksy.
```

## What can an AI agent do in Booksy?

Cotlet is best for Booksy owners of barbershops and salons who want their AI agent to handle the calendar, time off, reports and win-back messages without running or fixing a server.

- **Review tomorrow's appointments** (runs: daily): "What does my Booksy calendar look like tomorrow? Tell me where the gaps are." → `list_appointments`, `find_open_slots`
- **[Bulk reschedule appointments when a staff member is out](https://cotlet.dev/integrations/booksy-api-mcp-server/bulk-reschedule-appointments)**: "Kate called in sick for Thursday. Block her day in Booksy and move each of her clients to another barber that day, or to Kate's next free slot if nobody else is free. Show me the plan before you move anyone." → `list_staff`, `add_time_off`, `list_appointments`, `get_appointment`, `list_services`, `find_open_slots`, `reschedule_appointment`
- **Block time off in the calendar**: "Block next Monday as time off for Kate." → `list_staff`, `add_time_off`
- **[Weekly staff revenue report](https://cotlet.dev/integrations/booksy-api-mcp-server/weekly-staff-revenue-report)** (runs: weekly): "Every Monday at 8 am, send me last week's revenue, tips and appointments per staff member from Booksy, compared with the week before, and flag anyone whose cancellations went up." → `get_report`
- **[Win back clients who have not booked](https://cotlet.dev/integrations/booksy-api-mcp-server/win-back-lapsed-clients)** (runs: weekly): "Find Booksy clients who have not been in for 45 days and have nothing booked, and send them an email about our Thursday Happy Hour. Show me the list and the text first." → `list_clients`, `list_appointments`, `send_message_blast`

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

Yes. Cotlet does not replace your automation platform: it gives it a Booksy 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 review tomorrow's appointments, 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 to https://cotlet.dev/api/v1/booksy/{tool}. | Schedule Trigger node. |
| Make | HTTP module: POST https://cotlet.dev/api/v1/booksy/{tool} with an Authorization: Bearer header and a JSON body. | Scenario schedule. |
| Zapier | Webhooks by Zapier: POST https://cotlet.dev/api/v1/booksy/{tool} with the same header and body. | Schedule by Zapier trigger. |
| Your own script | POST https://cotlet.dev/api/v1/booksy/{tool} with your API key. | cron or GitHub Actions. |

## Tools

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

### list_appointments

Appointments in a date range with client, service, staff, time and status. Access: read. REST: `POST /api/v1/booksy/list_appointments`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `from` | date | yes | First day, inclusive. |
| `to` | date | yes | Last day, inclusive. |
| `staff_id` | string | no | Only one staff member, from list_staff. |
| `cursor` | string | no | Next page cursor from the previous call. |

Lists appointments from your Booksy calendar between two days, in start order. Limit it to one staff member to see a single calendar. Each item has the client, service, staff member, start, end and status, and get_appointment returns the rest.

Example response:

```json
{
  "appointments": [
    {
      "appointment_id": "apt_58213904",
      "client": "Anna Novak",
      "service": "Haircut",
      "staff": "Tom",
      "start": "2026-10-12T10:00:00-04:00",
      "end": "2026-10-12T10:45:00-04:00",
      "status": "confirmed"
    },
    {
      "appointment_id": "apt_58213977",
      "client": "Mark Ellis",
      "service": "Beard trim",
      "staff": "Tom",
      "start": "2026-10-12T11:30:00-04:00",
      "end": "2026-10-12T12:00:00-04:00",
      "status": "confirmed"
    }
  ],
  "next_cursor": null
}
```

### get_appointment

One appointment: services, staff, price, client and notes. Access: read. REST: `POST /api/v1/booksy/get_appointment`.

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

Returns one appointment with its services, staff member, price, client and internal notes. Use it before changing an appointment.

Example response:

```json
{
  "appointment_id": "apt_58213904",
  "client": {
    "client_id": "cl_1042",
    "name": "Anna Novak"
  },
  "services": [
    {
      "name": "Haircut",
      "price": 35
    }
  ],
  "staff": "Tom",
  "start": "2026-10-16T15:00:00-04:00",
  "end": "2026-10-16T15:45:00-04:00",
  "status": "confirmed",
  "note": "Prefers a scissor cut"
}
```

### find_open_slots

Free start times for a service on one day, based on working hours, breaks and time off. Access: read. REST: `POST /api/v1/booksy/find_open_slots`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `service_id` | string | yes | Service ID from list_services. |
| `date` | date | yes | Day to check. |
| `staff_id` | string | no | Only this staff member. Default: anyone who offers the service. |

Returns free start times for one service on one day, in time order. It follows working hours, breaks, time off and the duration and buffer set on the service. Limit it to one staff member or leave it open to anyone who offers the service.

Example response:

```json
{
  "date": "2026-10-17",
  "service": "Haircut",
  "slots": [
    {
      "start": "2026-10-17T10:00:00-04:00",
      "staff_id": "stf_2291"
    },
    {
      "start": "2026-10-17T11:30:00-04:00",
      "staff_id": "stf_2291"
    }
  ]
}
```

### list_clients

Clients with contact details and last visit. Access: read. REST: `POST /api/v1/booksy/list_clients`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `query` | string | no | Name, email or phone to search for. |
| `not_visited_days` | integer | no | Only clients whose last visit is older than this many days. |
| `limit` | integer | no | Page size. Default: 50. |
| `cursor` | string | no | Next page cursor from the previous call. |

Lists clients from your client list with contact details and the date of the last visit. Search by name, email or phone, or keep only clients who have not visited for a number of days. Pages are cursor based.

Example response:

```json
{
  "clients": [
    {
      "client_id": "cl_1042",
      "name": "Anna Novak",
      "email": "anna@example.com",
      "last_visit": "2026-07-28"
    },
    {
      "client_id": "cl_1187",
      "name": "Mark Ellis",
      "email": "mark@example.com",
      "last_visit": "2026-07-30"
    }
  ],
  "next_cursor": null
}
```

### get_client

One client card: contact details, notes and appointment history. Access: read. REST: `POST /api/v1/booksy/get_client`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `client_id` | string | no | Client ID from list_clients. |
| `email` | string | no | Look up by email instead of ID. |

Returns one client card with contact details, notes and past appointments, newest first. Look the client up by ID or by email.

Example response:

```json
{
  "client_id": "cl_1042",
  "name": "Anna Novak",
  "email": "anna@example.com",
  "notes": "Prefers a scissor cut",
  "appointments": [
    {
      "appointment_id": "apt_58213904",
      "service": "Haircut",
      "start": "2026-10-16T15:00:00-04:00"
    }
  ]
}
```

### list_services

Your service menu with duration, price and the staff who offer each. Access: read. REST: `POST /api/v1/booksy/list_services`.

No parameters.

Returns the services on your Booksy menu with duration, price and the staff members who offer each one. Use the service ID in find_open_slots and create_appointment.

Example response:

```json
{
  "services": [
    {
      "service_id": "svc_301",
      "name": "Haircut",
      "duration_minutes": 45,
      "price": 35,
      "staff_ids": [
        "stf_2291",
        "stf_2305"
      ]
    },
    {
      "service_id": "svc_302",
      "name": "Beard trim",
      "duration_minutes": 30,
      "price": 20,
      "staff_ids": [
        "stf_2291"
      ]
    }
  ]
}
```

### list_staff

Staff members with their working hours and the services they offer. Access: read. REST: `POST /api/v1/booksy/list_staff`.

No parameters.

Returns your staff members with their weekly working hours and the services each one offers. Use the staff ID in other tools.

Example response:

```json
{
  "staff": [
    {
      "staff_id": "stf_2291",
      "name": "Tom",
      "services": [
        "Haircut",
        "Beard trim"
      ],
      "hours": {
        "mon": "09:00-18:00",
        "tue": "09:00-18:00"
      }
    },
    {
      "staff_id": "stf_2305",
      "name": "Kate",
      "services": [
        "Haircut"
      ],
      "hours": {
        "mon": "10:00-19:00",
        "tue": "10:00-19:00"
      }
    }
  ]
}
```

### get_report

Numbers from Stats & Reports for a period, as JSON. Access: read. REST: `POST /api/v1/booksy/get_report`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `category` | enum | yes | dashboard, revenue, appointments, clients, cash_flow, inventory, staff_members or marketing. The last four need Booksy Biz Pro. |
| `from` | date | yes | First day, inclusive. |
| `to` | date | yes | Last day, inclusive. |

Returns the numbers of one Stats & Reports category for a date range. Booksy Biz Lite has Dashboard, Revenue, Appointments and Clients; Cash Flow, Inventory, Staff Members and Marketing need Booksy Biz Pro, and the call fails for other plans.

Example response:

```json
{
  "category": "staff_members",
  "from": "2026-10-05",
  "to": "2026-10-11",
  "total": {
    "revenue": 4820,
    "appointments": 96
  },
  "staff": [
    {
      "name": "Tom",
      "revenue": 2310,
      "appointments": 41
    },
    {
      "name": "Kate",
      "revenue": 1640,
      "appointments": 33
    },
    {
      "name": "Sam",
      "revenue": 870,
      "appointments": 22
    }
  ]
}
```

### create_appointment

Book a client into your calendar. Access: write, asks the user first. REST: `POST /api/v1/booksy/create_appointment`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `client_id` | string | yes | Client ID from list_clients or add_client. |
| `service_id` | string | yes | Service ID from list_services. |
| `start` | datetime | yes | ISO 8601 with time zone. |
| `staff_id` | string | no | Staff member. Default: first one free. |
| `note` | string | no | Internal note on the appointment. |

Books one client for one service at a start time. Pick a start from find_open_slots. Booksy applies its automatic confirmation and the client is part of the booking. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "appointment_id": "apt_58214120",
  "status": "confirmed",
  "client": "Mark Ellis",
  "service": "Beard trim",
  "staff": "Tom",
  "start": "2026-10-20T10:00:00-04:00",
  "end": "2026-10-20T10:30:00-04:00"
}
```

### reschedule_appointment

Move an appointment to a new time or staff member. Access: write, asks the user first. REST: `POST /api/v1/booksy/reschedule_appointment`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `appointment_id` | string | yes | Appointment ID from list_appointments. |
| `start` | datetime | yes | New start, ISO 8601 with time zone. |
| `staff_id` | string | no | New staff member. Default: unchanged. |

Moves one appointment to a new start time and optionally to another staff member. Booksy booking rules that limit rescheduling still apply, so the call can be refused. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "appointment_id": "apt_58213904",
  "status": "confirmed",
  "service": "Haircut",
  "staff": "Tom",
  "start": "2026-10-17T11:30:00-04:00",
  "end": "2026-10-17T12:15:00-04:00"
}
```

### add_client

Add a client card to your client list. Access: write. REST: `POST /api/v1/booksy/add_client`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `name` | string | yes | Full name. |
| `phone` | string | no | Phone in international format. |
| `email` | string | no | Email address. |
| `note` | string | no | Internal note. |

Adds one client card with a name and optional phone, email and note. It reaches no one and you can edit the card in Booksy, so add_client runs without asking first.

Example response:

```json
{
  "client_id": "cl_1310",
  "name": "Lena Fox",
  "email": "lena@example.com"
}
```

### add_time_off

Block time in a staff member's calendar so no one can book it. Access: write. REST: `POST /api/v1/booksy/add_time_off`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `staff_id` | string | yes | Staff ID from list_staff. |
| `start` | datetime | yes | ISO 8601 with time zone. |
| `end` | datetime | yes | ISO 8601 with time zone. |
| `reason` | string | no | Internal label, e.g. vacation. |

Blocks a period in one staff member's calendar, like time off set in the app, so no one can book during it. It reaches no client and you can remove the block in Booksy, so add_time_off runs without asking first.

Example response:

```json
{
  "time_off_id": "to_7714",
  "staff_id": "stf_2291",
  "start": "2026-10-19T09:00:00-04:00",
  "end": "2026-10-19T18:00:00-04:00",
  "reason": "vacation"
}
```

### send_message_blast

Send one message to chosen clients by email, SMS or push notification. Access: write, asks the user first. REST: `POST /api/v1/booksy/send_message_blast`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `channel` | enum | yes | email, sms or push. |
| `message` | string | yes | Message text. |
| `client_ids` | string[] | yes | Recipients from list_clients. |

Sends one Message Blast to the clients you list, by email, SMS or a push notification to the Booksy Client App. SMS comes from an automated number, so clients cannot reply, and Booksy adds a link to your profile at the bottom. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "blast_id": "mb_2208",
  "channel": "email",
  "recipients": 3,
  "status": "sent"
}
```

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

Connecting Booksy takes three steps: request access, sign in to Booksy once, then add one MCP server or call the REST API with the same key.

### Connect Booksy to your agent.

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

2. **Sign in to Booksy once** Open the connect page from the console and sign in to Booksy the way you always do. We keep the session, never your password, and you can revoke it anytime.

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

```
What does my Booksy calendar look like tomorrow? Tell me where the gaps are.
```

### Call Booksy 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 a POST endpoint at /api/v1/booksy/{tool}. Send its parameters as JSON, exactly as listed in the endpoints above.

```
curl https://cotlet.dev/api/v1/booksy/reschedule_appointment \
  -H "Authorization: Bearer $COTLET_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"appointment_id":"apt_58213904","start":"2026-10-17T11:30:00-04:00","staff_id":"stf_2291"}'
```

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

```
{
  "appointment_id": "apt_58213904",
  "status": "confirmed",
  "service": "Haircut",
  "staff": "Tom",
  "start": "2026-10-17T11:30:00-04:00",
  "end": "2026-10-17T12:15:00-04:00"
}
```

## Why use Cotlet for Booksy?

**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 Booksy yourself. We keep only the session, encrypted with AES-256.
- The model never sees a login.
- No stored passwords, no CAPTCHA solving, no MFA bypass.

**You stay in control**

- Pick read only, or read and write.
- Anything that reaches other people waits for your OK, unless you switch it off per tool.
- Revoke access in one click.

**Kept working for you**

- We test every integration daily.
- When Booksy changes, the tool pauses until we fix it.
- Failed calls cost nothing.

## Is there a Booksy MCP server on GitHub?

We found no Booksy MCP server. Owners who want bookings in another tool forward Booksy confirmation emails to a Zapier email parser, which gives one-way copies of new bookings only.

|  | Zapier email parser | Cotlet |
|---|---|---|
| Setup | Forward Booksy emails to a parser and map the fields | Request access, sign in to Booksy Biz once, add one MCP server or API key |
| What it can do | Copy new bookings into another calendar | Read and change appointments, clients, time off and reports |
| Changes in Booksy | None: it only reads emails | Book, reschedule, add time off and send blasts, each confirmed by you where others are reached |
| When the email layout changes | The parser breaks until you fix it | Our team tests it daily and fixes it for you; failed calls are free |
| Your Booksy session | Not used | Encrypted in an EU vault, never your password, revoked in one click |
| Where it runs | Zapier | Hosted: Claude Code, Codex, Cursor, n8n and scripts, also on a schedule |
| Price | Zapier plan, free tier for a few tasks | Free 7-day trial with 5,000 credits, then credits per call |

### 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 Booksy 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 the session to stay on your own computer
- you only need it now and then, from one MCP client

## How much does the Booksy API cost?

Free 7-day trial with 5,000 credits, no card needed. After that, the Booksy API comes with the Cotlet plan, from $29 a month for 3,000 credits, with no limit on apps. Each month's credits stay valid for 3 months, so unused credits add up.

| Size | Price | Credits / month | Per credit |
|---|---|---|---|
| Solo | $29/mo | 3,000 | about $0.0097 |
| Pro | $99/mo | 12,000 | about $0.0083 |
| Agency | $299/mo | 40,000 | $0.0075 |

Each successful call uses credits for the work it takes; failed calls and timeouts cost nothing. A hard spend cap is on by default. Authenticate with the `Authorization: Bearer` header. [See full pricing](https://cotlet.dev/pricing)

## How Cotlet holds your access

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

- **Company details:** The legal name, address and registration numbers of the company behind Cotlet are in the Terms of service. [Terms](https://cotlet.dev/terms)
- **Your session:** You sign in to Booksy yourself, in your browser. We keep only the session, never your password: encrypted with AES-256 in an EU vault, isolated to your account and used only when your agent calls a Booksy tool you allowed. When it expires, your agent gives you a link to sign in again. [Security](https://cotlet.dev/security)
- **Revoking access:** Disconnect Booksy in your dashboard: the session is deleted and access ends at once. 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.
- **Booksy's terms:** You use your own Booksy account and stay responsible for following Booksy's terms. Cotlet is independent and not affiliated with Booksy. [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?**

Request access and pick Booksy. Cotlet reviews each request and emails you your API key.

**Do I need to be technical?**

No. You sign in to Booksy once in your browser 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 a hosted server safe? My Booksy session would leave my computer.**

Cotlet keeps your Booksy session encrypted with AES-256 in an EU vault, isolated to your account and used only for the tools you allow: read only, or read and write. The AI model never sees it, and you revoke it in one click. A local server keeps the same session in a file on your computer, readable by any program you run, and needs a fresh sign-in whenever it expires.

**Do I need Booksy Biz Pro?**

Only for some reports. Booksy Biz Lite has Dashboard, Revenue, Appointments and Clients reports; Cash Flow, Inventory, Staff Members and Marketing need Pro. Calendar, client and Message Blast tools do not depend on those reports.

**Can my agent send a Message Blast on its own?**

Yes, once you switch confirmation off for send_message_blast. By default you confirm each blast, because it reaches your clients. Booksy includes 2,000 marketing text messages per month in the subscription.

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

No. Every call to create_appointment, reschedule_appointment or send_message_blast waits for your OK by default. For scheduled automations you can switch confirmation off per tool in your dashboard, for example only for approvals. add_client, add_time_off runs without asking, because it sends nothing to anyone and one call undoes it.

**Can I use the Booksy API in n8n?**

Yes. Add https://cotlet.dev/mcp/v1 with your API key in n8n's MCP Client node, or call https://cotlet.dev/api/v1/booksy/{tool} from the HTTP Request node.