[Cotlet](https://cotlet.dev/index.md) · [Integrations](https://cotlet.dev/integrations.md) · [How it works](https://cotlet.dev/how-it-works.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)

# Salonized API and MCP server: Let your AI agent run your Salonized calendar.

> Salonized has no public API, no webhooks and no MCP server (checked 31 Oct 2026). Its help center has no article on any of them. Cotlet runs 12 Salonized tools hosted, over MCP for agents and REST for scripts.

Appointments, customers, waiting list and sales for your Salonized salon. Use it in ChatGPT, Claude or any AI agent over MCP, or in n8n, Make and scripts over REST.

[MCP setup](https://cotlet.dev/integrations/salonized-api-mcp-server.md#connect)
[REST API guide](https://cotlet.dev/integrations/salonized-api-mcp-server.md#rest-api)

- Free 7-day trial, no card
- Unofficial, not affiliated with Salonized
- Page: https://cotlet.dev/integrations/salonized-api-mcp-server

## What can you automate in Salonized?

- Book an appointment by chat
- Send tomorrow's list to your team
- Fill gaps from the waiting list
- Save notes and colour formulas
- Log no-shows
- Copy weekly sales to a sheet

## Does Salonized have an MCP server or an API?

- No Zapier or n8n page for Salonized exists, and the help center finds no article on Zapier or webhooks.
- The official connections are Google and Apple calendar sync, Stripe, Reserve with Google and the Treatwell Marketplace. None of them reads customers or books for an agent.
- A 2018 wiki on GitHub lists endpoints for the online booking widget only. The repository behind it is empty.

| What you need | Calendar sync | Your own script | Cotlet |
|---|---|---|---|
| Read appointments | Into Google or Apple calendar | If you write it | Yes, any range |
| Book an appointment | No | Widget endpoints only | Yes, after your OK |
| Customer notes and no-shows | No | If you write it | Yes |
| Waiting list and sales totals | No | If you write it | Yes, Basic plan and up |
| Clear in the terms | Yes, official | Unclear | Uses the web app, see Terms |

Checked 31 Oct 2026. Sources: [Salonized help center: search results for "api"](https://help.salonized.com/en/?q=api), [Salonized public-api wiki: Bookings API (2018)](https://github.com/salonized/public-api/wiki/Bookings-API), [Salonized help: Reports explained](https://help.salonized.com/en/articles/573207-reports-explained), [Salonized pricing](https://www.salonized.com/en/pricing)

## How does Cotlet connect to Salonized?

1. **Sign in to Salonized.** Use your own account in its Cotlet Cloud Browser.
2. **Choose MCP or REST.** Connect your agent or create a Cotlet API key.
3. **Run your workflow.** Ask your agent or send an HTTP request.

We never keep your Salonized password, and nothing that reaches a customer happens until you approve it.

## Connect Salonized to your agent or workflow

Use MCP with your AI agent, or HTTP requests in n8n, Make, Zapier and scripts. Follow the MCP setup below or jump to the REST guide.

1. **Enable Salonized for agents.** Sign up, log in to Salonized in its Cloud Browser, then press Enable for agents.
2. **Add the Cotlet address.** Add https://cotlet.dev/mcp/v1 as an MCP server or connector in your agent.
3. **Approve the connection.** Chat apps ask you to sign in to Cotlet. Editors, n8n and scripts use an API key from the console.

One shared address, `https://cotlet.dev/mcp/v1`, also carries Salonized next to your other apps. If you enable Salonized after connecting, refresh the connector so the new tools show up.

Claude:

```
Settings > Connectors > Add custom connector
URL: https://cotlet.dev/mcp/v1/connect

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

ChatGPT:

```
Settings > Apps & Connectors > Create
MCP server URL: https://cotlet.dev/mcp/v1/connect
Authentication: OAuth
```

Cursor:

```
// ~/.cursor/mcp.json
{
  "mcpServers": {
    "cotlet-salonized": {
      "url": "https://cotlet.dev/mcp/v1",
      "headers": { "Authorization": "Bearer ${env:COTLET_API_KEY}" }
    }
  }
}
```

Codex:

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

n8n:

```
MCP Client Tool (inside an AI Agent)
Transport: HTTP Streamable
URL: https://cotlet.dev/mcp/v1
Auth: Bearer, <your key>
Tool: salonized_read
```

Make, Zapier:

```
Make: MCP Client > Call a tool
Zapier: MCP Client by Zapier > Run Tool
Server URL: https://cotlet.dev/mcp/v1
Token: <your key>
Tool: salonized_write
```

## How to use the Salonized REST API

### Create your Cotlet API key

Create a Cotlet API key with access to Salonized and its read operations. Store it as `COTLET_API_KEY` in your environment or automation platform's credential store.

Connect Salonized in Cotlet and enable it for agents. Account access: Your own Salonized login (the calendar, customers and Reports menus must be visible to that user; reports and the waiting list need the Basic plan or higher).

### Make your first Salonized API request

REST:

```
curl "https://cotlet.dev/api/v1/salonized/appointments?from=2026-11-05&to=2026-11-06" \
  -H "Authorization: Bearer $COTLET_API_KEY"
```

### Read appointments and apply the operation limits

A successful REST call puts the tool output in `result`. This illustrative response excerpt omits call IDs, messages and credit details.

Illustrative response excerpt:

```
{
  "status": "success",
  "app": "salonized",
  "tool": "list_appointments",
  "result": {
    "appointments": [
      {
        "appointment_id": "48213907",
        "start": "2026-11-05T10:00",
        "customer": {
          "customer_id": "9120345",
          "name": "Sanne de Vries"
        },
        "services": [
          {
            "name": "Cut and finish",
            "price": 45
          }
        ],
        "employee": "Eva Bakker",
        "no_show": false
      }
    ]
  }
}
```

Returns each appointment in the date range with customer, services with price, employee and no-show flag, ordered by start time.

Absences and breaks are not appointments and are not returned.

Replace the dates with your own range; add `employee` to read one person's calendar.

Keep the appointment ID in your workflow so a later run updates the same record.

### Salonized workflows for agents and automations

| Tool | Connect through | Example workflow |
|---|---|---|
| n8n | HTTP Request | Read tomorrow's appointments with `list_appointments` and post them to a team channel every evening. |
| Make | HTTP > Make a request | Read the Totals of a week with `get_sales_report` and add them to a bookkeeping sheet. |
| Python or Node.js | REST API | Read `list_waiting_list` for a day and compare it with `list_appointments` to find gaps for your review. |

Send `Authorization: Bearer <your Cotlet API key>` in request headers. You configure the schedule, destination and record comparisons.

Cotlet reads Salonized; your workflow steps write to your chosen destination. These HTTP workflows do not require a native Cotlet connector or a prebuilt template.

Python and Node.js can use the same HTTP requests without an AI agent. Keep access keys in credentials, outside shared workflow exports.

The [API and MCP reference](https://cotlet.dev/integrations/salonized-api-mcp-server.md#tools) lists operations and inputs. The [REST API guide](https://cotlet.dev/docs/api.md) explains authentication, errors and approvals.

## Salonized API endpoints and MCP tools

### Calendar and services

Reads the calendar as you see it. Absences and breaks are not appointments.

- **List appointments** (`list_appointments`, read): List calendar appointments in a date range, with customer, services, employee and time.
- **Get an appointment** (`get_appointment`, read): Read one appointment with its note and total.
- **List services** (`list_services`, read): List the services of the salon with their price.
- **Book an appointment** (`create_appointment`, write, asks first): Add an appointment to the calendar for a customer.
- **Mark a no-show** (`mark_no_show`, write, asks first): Mark an appointment as a no-show.

### Customers and notes

Notes can carry a follow-up date that shows in the calendar. Archived customers are not searched.

- **Find a customer** (`find_customer`, read): Search the customer file by name, email or mobile number.
- **Get a customer profile** (`get_customer`, read): Read a customer profile with notes and recent appointments.
- **Add a customer** (`add_customer`, write): Create a customer profile.
- **Add a customer note** (`add_customer_note`, write): Add a note to a customer profile, with an optional follow-up date.

### Waiting list and sales

The waiting list needs Basic or Pro. The sales report reads the Totals tab of Reports.

- **List the waiting list** (`list_waiting_list`, read): List waiting list sign-ups for a day.
- **Add to the waiting list** (`add_to_waiting_list`, write): Add a customer to the waiting list for a day.
- **Get a sales report** (`get_sales_report`, read): Read the Totals report of the Reports page for a period.

Inputs, REST path and example response of every tool: https://cotlet.dev/integrations/salonized-api-mcp-server#tools

## Who can see my Salonized session, and how do I revoke it?

- **What we store.** Your logged-in Salonized profile, encrypted with AES-256-GCM, in Finland. Not the password.
- **What your agent gets.** The 12 Salonized tools. Never the cookie.
- **What the session sees.** Your salon: calendar, customer files, waiting list, reports.
- **What no tool touches.** Checkout, payments, plan, password and deleting.
- **If Salonized asks to verify.** You sign in yourself in the Cloud Browser. We never type a code for you.
- **How to cut access.** Disable for agents, reset the browser, or change your Salonized password.

Our site scores A+ on Qualys SSL Labs, securityheaders.com and Mozilla Observatory ([live results](https://cotlet.dev/security.md)). There is no SOC 2 report or third-party pentest yet.

## Is it against Salonized's terms? Account safety

> The Customer is obliged to use the Services within the limits of the provisions of the Agreement and these General Terms and Conditions, as well as the applicable statutory regulations.
>
> [Salonized General Terms and Conditions, copy of 1 Jun 2021](https://web.archive.org/web/20210601/https://www.salonized.com/en/terms-and-conditions)

The terms page on salonized.com shows no text today (checked 31 Oct 2026), so this is the last copy we could read. It has no clause on bots, scraping or automated access, and we found no public case of a Salonized account closed for automation. Salonized is owned by Treatwell, and its terms may have changed since 2021. Cotlet works through the Salonized web app, and Salonized could still read it as automation.

How we keep your account looking like you:

- Your own salon account, logged in by you
- One Cloud Browser with its own IP and cookies, so no new-device check every call
- Anything that reaches a customer waits for your OK
- No tool deletes a customer or an appointment
- If Salonized objects, we pause the Salonized tools for everyone within 24 h

> Your salon data includes your customers' personal data. Salonized offers a data processing agreement; check that it covers a tool you let act in your account.

## What happens when Salonized changes?

- **12 h** between tests of the Salonized reads
- **$0** for a call to a Salonized tool paused for repair

When Salonized moves a button or renames a field, the fix happens on our side and your prompts keep working. [status.cotlet.dev](https://status.cotlet.dev) watches the site, console and API every 3 minutes.

## Approvals, undo and mistakes

1. **Finds the customer.** Several matches stop the run and the agent asks.
2. **Checks the calendar.** Reads the day so no booking lands on another one.
3. **Waits for your OK.** The booking shows up in your Cotlet console first.
4. **Reports the booking.** Appointment ID, time, services, total, email sent or not.

| Action | Undo |
|---|---|
| Book an appointment | Delete it in the calendar; a confirmation email already sent stays sent |
| Mark a no-show | Untick no-show in Edit; an automatic email already sent stays sent |
| Add a customer note | Delete the note in the profile |
| Add a customer | Archive the customer |
| Add to the waiting list | Remove the entry on the Waiting List page |

2 of 12 tools ask first: create_appointment and mark_no_show, the two that can email a customer. Notes, new customers and waiting list entries reach nobody, so they run at once. Switch the wait off per tool for a scheduled run.

> create_appointment sends no email unless you set send_email_notifications.

MCP call:

```
{
  "name": "create_appointment",
  "arguments": {
    "customer_id": "9120345",
    "services": [
      "Cut and finish"
    ],
    "start": "2026-11-05T10:00",
    "employee": "Eva Bakker",
    "send_email_notifications": false
  }
}
```

REST:

```
curl -X POST https://cotlet.dev/api/v1/salonized/customers/9120345/appointments \
  -H "Authorization: Bearer $COTLET_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"services":["Cut and finish"],"start":"2026-11-05T10:00","employee":"Eva Bakker","send_email_notifications":false}'
```

Tool output:

```
{
  "appointment_id": "48213907",
  "start": "2026-11-05T10:00",
  "customer_id": "9120345",
  "services": [
    {
      "name": "Cut and finish",
      "price": 45
    }
  ],
  "employee": "Eva Bakker",
  "total": 45,
  "email_sent": false
}
```

Scripts and cron jobs reach the same tools over REST at `/api/v1/salonized`, with the same key and price. A failed call costs nothing. The tools table lists the REST path of each tool.

## How much does the Salonized MCP server cost?

**About $47 a month** for a small salon with 3 employees, 8,140 credits. Your Salonized plan is billed by Salonized as before.

| Job | Calls | Credits |
|---|---|---|
| Book an appointment by chat | 3 × 120 | 3,600 |
| List tomorrow's appointments, daily | 1 × 30 | 300 |
| Match the waiting list to gaps | 3 × 30 | 900 |
| Save a customer note | 2 × 60 | 1,200 |
| Log a no-show | 3 × 20 | 600 |
| Weekly sales totals | 1 × 4 | 40 |
| Cloud Browser, 30 days |  | 1,500 |
| Total |  | 8,140 |

- Free 7-day trial, no card
- 10 credits per successful call, MCP or REST
- 50 credits a day for the Cloud Browser
- Works on any Salonized plan that shows the screen

The month is our example: 3 employees, about 20 appointments a day, 120 chat bookings. Salonized publishes no typical account size. Dollars at the $29 pack rate.

## Salonized MCP server on GitHub, Zapier or hosted: which to use

| Option | What it does | Where it stops |
|---|---|---|
| [SabbeRubbish/gatsby-source-salonized](https://github.com/SabbeRubbish/gatsby-source-salonized) | Pulls Salonized data into a Gatsby site with a cookie login. | Not an MCP server, 2 stars, last commit 11 Mar 2021. |
| [Salonized public-api wiki](https://github.com/salonized/public-api/wiki/Bookings-API) | Lists the booking widget endpoints, last edited July 2018. | Booking widget only; the repository is empty. |
| Zapier, Make, n8n | No Salonized app found on Zapier or n8n; the Make page was not reachable. | Nothing to call from a workflow. |
| Data export and CSV import | Salonized's own Settings > Data export and customer import. | By hand, one period at a time, no booking. |

There is no Salonized MCP server on GitHub and no hosted one besides ours. Doing it by hand needs no setup and costs your time. Switching software costs a migration. Cotlet keeps your Salonized account and lets an agent do the booking, notes and reporting chores.

## Who runs Cotlet

Take Group sp. z o.o. runs Cotlet. It is a software company registered in Poland, EU (VAT PL6342984273), working since 2019, founded by Bart Krawczyk (Co-founder, CTO) and Jake Slugocki (Co-founder, SEO, sales and marketing). Write to contact@cotlet.dev with questions about the Salonized tools.

## Salonized API and MCP: questions

### How do I get access?

Create a free account at https://cotlet.dev, open Salonized under Integrations in the console and log in to Salonized in its Cloud Browser. The trial starts with your first app, no card asked.

### How do I connect Salonized to ChatGPT or Claude?

Sign up at cotlet.dev, log in to Salonized once in its Cloud Browser and add Cotlet to ChatGPT or Claude, following the steps in your console. No API key is needed. ChatGPT and Claude then work in your Salonized account through Cotlet, in their phone apps too.

### What can ChatGPT do in Salonized?

With Cotlet, ChatGPT, Claude and other AI agents handle jobs like these in Salonized: book salon appointments with AI; send tomorrow\; fill open slots from the waiting list. You ask in plain words, and anything that reaches other people waits for your OK first.

### Which Salonized plan do I need?

Cotlet acts as the signed-in user and sees what that user sees. Salonized's trial gives 14 days of Pro features; after that Appointments covers calendar and customers. The waiting list and the Reports page need Basic or higher (Salonized help center, checked 31 Oct 2026).

### Will my customers get an email?

Only if you ask. create_appointment takes send_email_notifications, off by default, which mirrors the box next to Save in the appointment form. mark_no_show can trigger the automatic no-show email if you set one up in Salonized. You confirm both by default.

### Can it move or cancel an appointment?

Not yet. The tools cover reading, booking, notes, no-shows and the waiting list. Moving, cancelling, checkout, payments, products, newsletters and deleting customers are not included.

### Does Salonized have webhooks?

Not that we found. The help center has no article on them, so nothing tells an agent about a new booking. Run your agent on a schedule instead, for example a daily list_appointments pass.

### Is the MCP server different from the REST API?

Only the door is different. Both expose the same 12 tools, inputs and answers, with one API key and one price. Agents use MCP; scripts and HTTP steps use REST.

### Is Cotlet affiliated with Salonized?

No. Cotlet is independent and not affiliated with Salonized or Treatwell.

### Can I use the Salonized API without an AI agent?

Yes. Call Cotlet's REST API from a script or an HTTP step in n8n, Make or Zapier with your Cotlet key. MCP is the alternative for AI agents; you do not need to connect an agent to use REST.

---

Give your AI agents your signed-in browser.

**Product:** [Integrations](https://cotlet.dev/integrations.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.dev is built by Bart Krawczyk and Jake Slugocki, the founders of Take Group sp. z o.o., ul. Wincentego Janasa 4, 40-855 Katowice, Poland. KRS 0000871398, NIP 6342984273, VAT EU: PL6342984273. [About us](https://cotlet.dev/about.md)

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.
