Bookibles API · unofficial, by Cotlet

Create your own Bookibles API

Bookibles: no API, developer docs or API keys found (checked 20 Nov 2026). With Cotlet you can build your own. Do a job once with your AI agent in your Bookibles 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 Bookibles session and returns only what your login can see.

Try it free now

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

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

curl
curl -X POST "https://cotlet.dev/api/v1/custom/bookings-for-week" \
  -H "Authorization: Bearer $COTLET_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"week_of": "2026-11-23"}'
Node.js
const url = "https://cotlet.dev/api/v1/custom/bookings-for-week";
const res = await fetch(url, {
  method: "POST",
  headers: {
    Authorization: `Bearer ${process.env.COTLET_API_KEY}`,
    "Content-Type": "application/json",
  },
  body: JSON.stringify({ week_of: "2026-11-23" }),
});
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/bookings-for-week",
    headers={"Authorization": f"Bearer {key}"},
    json={"week_of": "2026-11-23"},
)
data = res.json()["data"]
Response 200 OK · JSON
{
  "data": [
    {
      "day": "Tue",
      "time": "10:00",
      "customer": "Sam K.",
      "service": "Intro call",
      "status": "pending"
    },
    {
      "day": "Wed",
      "time": "14:00",
      "customer": "Ria T.",
      "service": "Coaching session",
      "status": "pending"
    }
  ]
}

01 Build

How do you build a Bookibles endpoint with Cotlet?

  1. Sign in to Bookibles in your Cloud Browser.

    You type your password yourself. Cotlet keeps the signed-in session, encrypted, never the password.

  2. Do the job once with your agent.

    For example: "List this week's bookings with the day, time, customer, service and status."

  3. Save it as an endpoint.

    Give it a name, choose its inputs, such as a week or a status, and the fields it returns.

  4. 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 Bookibles session.

02 Endpoints

Example endpoints you could build for Bookibles

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

  • POST /api/v1/custom/bookings-for-week

    Bookings for a week

    Day, time, customer, service and status for each booking

  • POST /api/v1/custom/pending-bookings

    Pending bookings

    Bookings still waiting for your confirmation

  • POST /api/v1/custom/services

    Your services

    Each service with its price and length

  • POST /api/v1/custom/new-messages

    New customer messages

    Messages with no reply yet, with the customer and date

  • POST /api/v1/custom/mark-no-show writes

    Mark a no-show

    The booking you name set to no-show

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

Request

curl -X POST "https://cotlet.dev/api/v1/custom/bookings-for-week" \
  -H "Authorization: Bearer $COTLET_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"week_of": "2026-11-23"}'

The answer is JSON, with your fields under data:

Response · 200 OK

{
  "data": [
    {
      "day": "Tue",
      "time": "10:00",
      "customer": "Sam K.",
      "service": "Intro call",
      "status": "pending"
    },
    {
      "day": "Wed",
      "time": "14:00",
      "customer": "Ria T.",
      "service": "Coaching session",
      "status": "pending"
    }
  ]
}

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

  • Schedule Cotlet endpoint Slack or email

    A Monday booking list in n8n or Make.

    This week's bookings, sent to Slack or email.

  • Schedule endpoint Email tool

    Follow-up lists.

    Customers with no new booking in 30 days, sent to your email tool.

  • Schedule endpoint Google Sheets

    A dashboard or a sheet.

    Bookings and no-shows by month, pulled into Google Sheets.

  • Chat agent endpoint pending bookings

    Your own assistant.

    A chat agent that checks pending bookings before it answers a customer.

04 Access

What can an endpoint see and change?

An endpoint works in your own Bookibles session, so it can read and change only what your Bookibles 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 marking a no-show, 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.

05 Official API

Does Bookibles have an official API?

Bookibles: no API, webhooks or data export found on bookibles.com or in its 7-article Help Center (checked 20 Nov 2026). The full picture with sources: Does Bookibles have an API or MCP server?

Want ChatGPT or Claude to work in Bookibles instead of code? See the Bookibles MCP server.

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.

Bookibles API with Cotlet: questions

Is this an official Bookibles API?

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

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

Build your first Bookibles endpoint

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

Try it free now

No card. Takes about 5 minutes.