[Cotlet](https://cotlet.dev/index.md) · [All integrations](https://cotlet.dev/integrations.md) · [MCP servers](https://cotlet.dev/integrations/mcp.md) · [APIs](https://cotlet.dev/integrations/api.md) · [API & MCP status](https://cotlet.dev/api-status.md) · [How it works](https://cotlet.dev/how-it-works.md) · [Security](https://cotlet.dev/security.md) · [Custom API](https://cotlet.dev/custom-api.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)

# Create your own Planfy API

> Planfy: no API yet; Planfy says its official API is in development. With Cotlet you build your own: do a job once with your AI agent, save it as an endpoint and call it from n8n or code.

Source: https://cotlet.dev/integrations/api/planfy

Planfy: no API yet. Planfy says "An official Planfy API is currently in development" (checked 20 Nov 2026). With Cotlet you can build your own. Do a job once with your AI agent in your Planfy account, save it as an endpoint, and call it from n8n, Make, Zapier or your own code. Each endpoint runs in your own signed-in Planfy session and returns only what your login can see.

[Try it free now](https://cotlet.dev/app/signup?app=planfy)

Free 7-day trial, 2,000 credits, no card

Cotlet is an independent service. It is not affiliated with, endorsed by or sponsored by Planfy. Planfy is a trademark of its owner. If Planfy's own integrations cover what you need, use them first.

curl Node.js Python

curl

```
curl -X POST "https://cotlet.dev/api/v1/custom/appointments-for-day" \
  -H "Authorization: Bearer $COTLET_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"date": "2026-11-26"}'
```

Node.js

```
const url = "https://cotlet.dev/api/v1/custom/appointments-for-day";
const res = await fetch(url, {
method: "POST",
headers: {
Authorization: `Bearer ${process.env.COTLET_API_KEY}`,
"Content-Type": "application/json",
},
body: JSON.stringify({ date: "2026-11-26" }),
});
const { data } = await res.json();
```

Python

```
import os
import requests

key = os.environ["COTLET_API_KEY"]
res = requests.post(
"https://cotlet.dev/api/v1/custom/appointments-for-day",
headers={"Authorization": f"Bearer {key}"},
json={"date": "2026-11-26"},
)
data = res.json()["data"]
```

Response 200 OK · JSON

```
{
"data": [
{
"time": "09:00",
"customer": "Joan B.",
"staff": "Ella",
"service": "Eye test",
"status": "booked"
},
{
"time": "10:30",
"customer": "Raj P.",
"staff": "Ella",
"service": "Contact lens check",
"status": "booked"
}
]
}
```

01 Build

## How do you build a Planfy endpoint with Cotlet?

1. 01  
www.planfy.com  
Signed in  
### Sign in to Planfy in your Cloud Browser.  
You type your password yourself. Cotlet keeps the signed-in session, encrypted, never the password.
2. 02  
List the appointments for a day with the customer, staff member and service.  
### Do the job once with your agent.  
For example: "List the appointments for a day with the customer, staff member and service."
3. 03  
Save endpoint  
Name  
appointments-for-day  
Input  
date  
Returns  
time, customer, staff, service, status  
### Save it as an endpoint.  
Give it a name, choose its inputs, such as a date or a staff member, and the fields it returns.
4. 04  
$ POST /api/v1/custom/appointments-for-day  
200 OK  
### Call it with your Cotlet API key.  
Each endpoint gets its own address, `POST https://cotlet.dev/api/v1/custom/<name>`. You send JSON in and get JSON back, from the same signed-in Planfy session.

02 Endpoints

## Example endpoints you could build for Planfy

Cotlet ships no fixed list of Planfy endpoints. You decide which endpoints you build and what each one returns.

- POST `/api/v1/custom/appointments-for-day`  
### Appointments for a day  
Time, customer, staff member, service and status
- POST `/api/v1/custom/recalls-due`  
### Recalls due  
Customers with a recall due in a period and whether they booked
- POST `/api/v1/custom/find-customer`  
### Find a customer  
Matching customers with phone, email and last visit
- POST `/api/v1/custom/free-slots`  
### Free slots  
Open times for a service and staff member on a day
- POST `/api/v1/custom/book-appointment` writes  
### Book an appointment  
A booking for the customer, service and time you name
- POST `/api/v1/custom/<name>`

A call to an endpoint you built could look like this:

Request

```
curl -X POST "https://cotlet.dev/api/v1/custom/appointments-for-day" \
  -H "Authorization: Bearer $COTLET_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"date": "2026-11-26"}'
```

The answer is JSON, with your fields under `data`:

Response · 200 OK

```
{
"data": [
{
"time": "09:00",
"customer": "Joan B.",
"staff": "Ella",
"service": "Eye test",
"status": "booked"
},
{
"time": "10:30",
"customer": "Raj P.",
"staff": "Ella",
"service": "Contact lens check",
"status": "booked"
}
]
}
```

When you save an endpoint, Cotlet gives you its curl example and an OpenAPI description to paste into n8n, Make or your code.

03 Uses

## What can you use your Planfy endpoints for?

- Schedule Cotlet endpoint Slack or email  
### A Monday recall list in n8n or Make.  
Recalls due this week and open slots, sent to Slack or email.
- Front desk endpoint free slots  
### A phone booking helper.  
Free slots read from Planfy while a customer is on the phone.
- Month end endpoint Google Sheets  
### A practice sheet.  
Appointments by staff member each month, pulled into Google Sheets.
- Voice or chat agent endpoint free slots  
### Your own AI receptionist.  
A voice or chat agent that checks free slots in Planfy before it offers a time.

04 Access

## What can an endpoint see and change?

An endpoint works in your own Planfy session, so it can read and change only what your Planfy login can. An owner login sees the whole business. A team login sees what its permissions allow. You choose what each endpoint does when you build it.

An endpoint that changes something, such as booking an appointment, first runs as a dry run: Cotlet shows you each request it would send, and nothing is sent. You allow the writes once in the Cotlet console and set a daily cap. A call over the cap fails whole, never half done.

DRY RUN · nothing sent

$ POST /api/v1/custom/book-appointment

would POST www.planfy.com/... book Joan B. for an eye test on Tuesday at 09:30

`book-appointment`writes

Allow writes

Daily cap 20 writes

05 Official API

## Does Planfy have an official API?

Planfy says its official API "is currently in development"; its only developer docs cover a JavaScript library for booking widgets (checked 20 Nov 2026). Customers export and import by file. The full picture with sources: [Does Planfy have an API or MCP server?](https://cotlet.dev/api-status/planfy.md)

Want ChatGPT or Claude to work in Planfy instead of code? See the [Planfy MCP server](https://cotlet.dev/integrations/planfy-api-mcp-server.md).

0/3

Official API

In development

[Full API & MCP report](https://cotlet.dev/api-status/planfy.md)

06 Pricing

## What does it cost?

per successful call

 10 credits

when a call fails

 0

in the smallest pack

≈ 500 calls

free trial, no card

 7 days

A call to your endpoint costs 10 credits when it succeeds and nothing when it fails, with no browser minutes on top. Credits come in one-time packs from $29 for 5,000 credits, so a pack covers about 500 successful calls. The free trial gives you 2,000 credits for 7 days, no card.

## Planfy API with Cotlet: questions

### Is this an official Planfy API?

No. Cotlet is independent and not affiliated with Planfy. The endpoints you build run in your own signed-in Planfy account.

### Do I need to code?

Not to build an endpoint: you do the job once with your agent and save it. To call it, you need a tool that sends HTTP requests, such as n8n, Make, Zapier or a script.

### What happens when Planfy changes its screens?

An endpoint works while Planfy works the way it did when you built it. If Planfy changes and a call fails, you get an email. After 3 failures in a row the endpoint turns off until you rebuild it with your agent or in the console. A failed call costs nothing.

### How long can a call take?

Up to 90 seconds, and the answer can be up to 1 MB of JSON.

POST /api/v1/custom/<name>

## Build your first Planfy endpoint

Sign in once, do the job with your agent and save it as an endpoint.

[Try it free now](https://cotlet.dev/app/signup?app=planfy)

No card. Takes about 5 minutes.

---

Give your AI agents your signed-in browser.

**Product:** [Integrations](https://cotlet.dev/integrations.md) · [MCP servers](https://cotlet.dev/integrations/mcp.md) · [APIs](https://cotlet.dev/integrations/api.md) · [API & MCP status](https://cotlet.dev/api-status.md) · [How it works](https://cotlet.dev/how-it-works.md) · [Pricing](https://cotlet.dev/pricing.md) · [Security](https://cotlet.dev/security.md) · [Custom API](https://cotlet.dev/custom-api.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.
