Shiftbase API · unofficial, by Cotlet

Create your own Shiftbase API

Shiftbase API tokens come with App Center+, a paid monthly add-on (checked 20 Nov 2026). With Cotlet you can build your own. Do a job once with your AI agent in your Shiftbase 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 Shiftbase 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 Shiftbase. Shiftbase is a trademark of its owner. If Shiftbase's own integrations cover what you need, use them first.

curl
curl -X POST "https://cotlet.dev/api/v1/custom/shifts-for-day" \
  -H "Authorization: Bearer $COTLET_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"date": "2026-11-21"}'
Node.js
const url = "https://cotlet.dev/api/v1/custom/shifts-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-21" }),
});
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/shifts-for-day",
    headers={"Authorization": f"Bearer {key}"},
    json={"date": "2026-11-21"},
)
data = res.json()["data"]
Response 200 OK · JSON
{
  "data": [
    {
      "employee": "Lena K.",
      "team": "Bar",
      "start": "07:00",
      "end": "11:00"
    },
    {
      "employee": "Tom H.",
      "team": "Kitchen",
      "start": "11:00",
      "end": "19:00"
    }
  ]
}

01 Build

How do you build a Shiftbase endpoint with Cotlet?

  1. Sign in to Shiftbase 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 tomorrow's shifts with the employee, team, start and end time."

  3. Save it as an endpoint.

    Give it a name, choose its inputs, such as a date or a team, 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 Shiftbase session.

02 Endpoints

Example endpoints you could build for Shiftbase

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

  • POST /api/v1/custom/shifts-for-day

    Shifts for a day

    Employee, team, start and end of each shift

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

    Hours waiting for approval

    Worked hours that are not approved yet, against the schedule

  • POST /api/v1/custom/leave-requests

    Leave requests

    Open requests with dates and who else is off

  • POST /api/v1/custom/hours-by-employee

    Hours by employee

    Worked and contract hours for a period

  • POST /api/v1/custom/approve-hours writes

    Approve hours

    The hours you name marked as approved

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

Request

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

The answer is JSON, with your fields under data:

Response · 200 OK

{
  "data": [
    {
      "employee": "Lena K.",
      "team": "Bar",
      "start": "07:00",
      "end": "11:00"
    },
    {
      "employee": "Tom H.",
      "team": "Kitchen",
      "start": "11:00",
      "end": "19:00"
    }
  ]
}

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

  • Schedule Cotlet endpoint Payroll

    A payroll file each month.

    Approved hours per employee sent to your accountant or payroll tool.

  • Schedule endpoint Team chat

    A morning rota in your team chat.

    Today's shifts posted to Slack or WhatsApp before opening.

  • Schedule endpoint Google Sheets

    A labour cost sheet.

    Hours per team pulled into Google Sheets next to your sales.

  • Chat agent endpoint free staff

    Your own AI assistant.

    A chat agent that checks who is free before it offers a cover shift.

04 Access

What can an endpoint see and change?

An endpoint works in your own Shiftbase session, so it can read and change only what your Shiftbase 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 approving hours, 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 Shiftbase have an official API?

Shiftbase has an API, and its pricing page lists API tokens under App Center+, an add-on at €20 a month, flat (checked 20 Nov 2026). The full picture with sources: Does Shiftbase have an API or MCP server?

Want ChatGPT or Claude to work in Shiftbase instead of code? See the Shiftbase 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.

Shiftbase API with Cotlet: questions

Is this an official Shiftbase API?

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

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