Skedda API · unofficial, by Cotlet
Create your own Skedda API
Skedda has a public API in beta, read only and on Skedda Premier and AllBooked Advanced plans (checked 20 Nov 2026). With Cotlet you can build your own. Do a job once with your AI agent in your Skedda 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 Skedda session and returns only what your login can see.
Free 7-day trial, 2,000 credits, no card
Cotlet is an independent service. It is not affiliated with, endorsed by or sponsored by Skedda. Skedda is a trademark of its owner. If Skedda's own integrations cover what you need, use them first.
curl -X POST "https://cotlet.dev/api/v1/custom/bookings-for-day" \
-H "Authorization: Bearer $COTLET_API_KEY" \
-H "Content-Type: application/json" \
-d '{"date": "2026-11-21"}' const url = "https://cotlet.dev/api/v1/custom/bookings-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(); import os
import requests
key = os.environ["COTLET_API_KEY"]
res = requests.post(
"https://cotlet.dev/api/v1/custom/bookings-for-day",
headers={"Authorization": f"Bearer {key}"},
json={"date": "2026-11-21"},
)
data = res.json()["data"] {
"data": [
{
"space": "Room 2",
"start": "09:00",
"end": "09:30",
"title": "Team stand-up",
"booked_by": "Ava L."
},
{
"space": "Room 4",
"start": "10:00",
"end": "11:00",
"title": "Client review",
"booked_by": "Ben K."
}
]
} 01 Build
How do you build a Skedda endpoint with Cotlet?
-
Sign in to Skedda in your Cloud Browser.
You type your password yourself. Cotlet keeps the signed-in session, encrypted, never the password.
-
Do the job once with your agent.
For example: "List tomorrow's bookings with space, time, title and who booked."
-
Save it as an endpoint.
Give it a name, choose its inputs, such as a date or a space, and the fields it returns.
-
Call it with your Cotlet API key.
Each endpoint gets its own address,
POST https://. You send JSON in and get JSON back, from the same signed-in Skedda session.cotlet.dev/ api/ v1/ custom/ <name>
02 Endpoints
Example endpoints you could build for Skedda
Cotlet ships no fixed list of Skedda endpoints. You decide which endpoints you build and what each one returns.
-
POST
/api/v1/custom/bookings-for-day Bookings for a day
Space, time, title and who booked, for each booking
-
POST
/api/v1/custom/booking-requests Booking requests
Requests waiting for approval, with space and time
-
POST
/api/v1/custom/bookings-per-space Bookings per space
How often each space was booked in a period
-
POST
/api/v1/custom/user-bookings A user's bookings
Bookings one person made in a period
-
POST
/api/v1/custom/writesapprove-request Approve a request
The approved booking, with its space and time
A call to an endpoint you built could look like this:
curl -X POST "https://cotlet.dev/api/v1/custom/bookings-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:
{
"data": [
{
"space": "Room 2",
"start": "09:00",
"end": "09:30",
"title": "Team stand-up",
"booked_by": "Ava L."
},
{
"space": "Room 4",
"start": "10:00",
"end": "11:00",
"title": "Client review",
"booked_by": "Ben K."
}
]
} 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 Skedda endpoints for?
- Schedule Cotlet endpoint Slack or email
A morning list in n8n or Make.
Today's bookings and waiting requests, sent to Slack or email before the doors open.
- Lobby screen endpoint bookings
A screen at the front desk.
Today's bookings per space, read from Skedda for a lobby display.
- Monthly endpoint Google Sheets
A usage sheet.
Bookings per space pulled each month into Google Sheets.
- Slack button endpoint approved booking
Approvals from chat.
A Slack button that approves a booking request after a manager says yes.
04 Access
What can an endpoint see and change?
An endpoint works in your own Skedda session, so it can read and change only what your Skedda 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 a request, 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 Skedda have an official API?
Skedda: the API (beta) "currently provides read-only access to booking data", on Premier and Advanced plans, and webhooks are on the same plans (checked 20 Nov 2026). Every venue can export bookings to XLSX or CSV. The full picture with sources: Does Skedda have an API or MCP server?
Want ChatGPT or Claude to work in Skedda instead of code? See the Skedda 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.
Skedda API with Cotlet: questions
Is this an official Skedda API?
No. Cotlet is independent and not affiliated with Skedda. The endpoints you build run in your own signed-in Skedda 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 Skedda changes its screens?
An endpoint works while Skedda works the way it did when you built it. If Skedda 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 Skedda endpoint
Sign in once, do the job with your agent and save it as an endpoint.
Try it free nowNo card. Takes about 5 minutes.