[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 Pikit API

> Pikit: no API found. 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/pikit

Pikit: no API found on pikit.io or in its documentation (checked 20 Nov 2026). With Cotlet you can build your own. Do a job once with your AI agent in your Pikit 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 Pikit session and returns only what your login can see.

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

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

Cotlet is an independent service. It is not affiliated with, endorsed by or sponsored by Pikit. Pikit is a trademark of its owner. If Pikit'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-27"}'
```

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-27" }),
});
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-27"},
)
data = res.json()["data"]
```

Response 200 OK · JSON

```
{
"data": [
{
"time": "09:00",
"client": "Lea M.",
"provider": "Nora",
"service": "Facial",
"status": "confirmed"
},
{
"time": "10:30",
"client": "Kim T.",
"provider": "Nora",
"service": "Brow lamination",
"status": "confirmed"
}
]
}
```

01 Build

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

1. 01  
app.pikit.io  
Signed in  
### Sign in to Pikit 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 client, provider and service.  
### Do the job once with your agent.  
For example: "List the appointments for a day with the client, provider and service."
3. 03  
Save endpoint  
Name  
appointments-for-day  
Input  
date  
Returns  
time, client, provider, service, status  
### Save it as an endpoint.  
Give it a name, choose its inputs, such as a date or a provider, 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 Pikit session.

02 Endpoints

## Example endpoints you could build for Pikit

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

- POST `/api/v1/custom/appointments-for-day`  
### Appointments for a day  
Time, client, provider, service and status for each appointment
- POST `/api/v1/custom/front-desk-today`  
### Today's front desk  
Who is expected, who has arrived and who needs checkout
- POST `/api/v1/custom/memberships-renewing`  
### Memberships renewing  
Members whose plan renews in a period
- POST `/api/v1/custom/find-client`  
### Find a client  
Matching clients with phone, email and last visit
- POST `/api/v1/custom/block-time` writes  
### Block time for a provider  
A blocked slot in that provider's calendar
- 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-27"}'
```

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

Response · 200 OK

```
{
"data": [
{
"time": "09:00",
"client": "Lea M.",
"provider": "Nora",
"service": "Facial",
"status": "confirmed"
},
{
"time": "10:30",
"client": "Kim T.",
"provider": "Nora",
"service": "Brow lamination",
"status": "confirmed"
}
]
}
```

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 Pikit endpoints for?

- Schedule Cotlet endpoint Slack or email  
### A morning report in n8n or Make.  
Today's appointments and memberships renewing, sent to Slack or email before opening.
- Website form endpoint free slots  
### A booking check on your website.  
Free slots for a service, read from Pikit when a visitor picks a day.
- Schedule endpoint Google Sheets  
### A memberships sheet.  
Members and renewals pulled into Google Sheets each week.
- Voice or chat agent endpoint free slots  
### Your own AI receptionist.  
A voice or chat agent that checks free slots in Pikit before it offers a time.

04 Access

## What can an endpoint see and change?

An endpoint works in your own Pikit session, so it can read and change only what your Pikit 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 blocking time, 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/block-time

would POST app.pikit.io/... block Nora 13:00 to 14:00 on Friday

`block-time`writes

Allow writes

Daily cap 20 writes

05 Official API

## Does Pikit have an official API?

Pikit: no API or developer docs found on pikit.io or in its documentation (checked 20 Nov 2026). Its integrations are fixed ones: calendars, Stripe, WordPress, GA4 and Meta Pixel. The full picture with sources: [Does Pikit have an API or MCP server?](https://cotlet.dev/api-status/pikit.md)

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

0/3

Official API

None found

[Full API & MCP report](https://cotlet.dev/api-status/pikit.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.

## Pikit API with Cotlet: questions

### Is this an official Pikit API?

No. Cotlet is independent and not affiliated with Pikit. The endpoints you build run in your own signed-in Pikit 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 Pikit changes its screens?

An endpoint works while Pikit works the way it did when you built it. If Pikit 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 Pikit 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=pikit)

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.
