Turno API · unofficial, by Cotlet
Create your own Turno API
Turno: the External API v2 is granted on request after you contact Turno; no self-serve key was found (checked 20 Nov 2026). With Cotlet you can build your own. Do a job once with your AI agent in your Turno 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 Turno 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 Turno. Turno is a trademark of its owner. If Turno's own integrations cover what you need, use them first.
curl -X POST "https://cotlet.dev/api/v1/custom/cleanings-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/cleanings-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/cleanings-for-day",
headers={"Authorization": f"Bearer {key}"},
json={"date": "2026-11-21"},
)
data = res.json()["data"] {
"data": [
{
"time": "11:00",
"property": "Beach House",
"type": "Turnover",
"cleaner": "Ana",
"status": "assigned"
},
{
"time": "12:30",
"property": "Harbor Loft",
"type": "Turnover",
"cleaner": null,
"status": "unassigned"
}
]
} 01 Build
How do you build a Turno endpoint with Cotlet?
-
Sign in to Turno 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 the cleanings on this day with the property, time, cleaner and status."
-
Save it as an endpoint.
Give it a name, choose its inputs, such as a date or a property, 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 Turno session.cotlet.dev/ api/ v1/ custom/ <name>
02 Endpoints
Example endpoints you could build for Turno
Cotlet ships no fixed list of Turno endpoints. You decide which endpoints you build and what each one returns.
-
POST
/api/v1/custom/cleanings-for-day Cleanings for a day
Property, time, type, cleaner and status of each cleaning
-
POST
/api/v1/custom/unassigned-cleanings Cleanings without a cleaner
Upcoming cleanings that still need someone, by date
-
POST
/api/v1/custom/cleaning-costs Cleaning costs for a period
Cost and time per property from the project report
-
POST
/api/v1/custom/property-checklist A property's checklist
The checklist items cleaners tick at that property
-
POST
/api/v1/custom/writesmove-cleaning Move a cleaning
A cleaning moved to a new time, with the new slot
A call to an endpoint you built could look like this:
curl -X POST "https://cotlet.dev/api/v1/custom/cleanings-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": [
{
"time": "11:00",
"property": "Beach House",
"type": "Turnover",
"cleaner": "Ana",
"status": "assigned"
},
{
"time": "12:30",
"property": "Harbor Loft",
"type": "Turnover",
"cleaner": null,
"status": "unassigned"
}
]
} 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 Turno endpoints for?
- Schedule Cotlet endpoint Slack or email
A weekly check in n8n or Make.
Next week's cleanings without a cleaner, sent to you by email or Slack.
- Schedule endpoint Google Sheets
A cost sheet.
Cleaning costs per property pulled into Google Sheets each month.
- Your tool endpoint owner report
Your own owner reports.
Cleanings done at each owner's property, for your monthly statement.
- Guest message endpoint cleaning time
A guest message flow.
Checks the cleaning time in Turno before your messaging tool confirms an early check-in.
04 Access
What can an endpoint see and change?
An endpoint works in your own Turno session, so it can read and change only what your Turno 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 moving a cleaning, 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 Turno have an official API?
Turno: the External API v2 docs say Turno "gives you access to your accounts data via our API" and ask you to contact Turno so it can grant access; every request carries a partner ID (checked 20 Nov 2026). Hosts can download project reports as a spreadsheet. The full picture with sources: Does Turno have an API or MCP server?
Want ChatGPT or Claude to work in Turno instead of code? See the Turno 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.
Turno API with Cotlet: questions
Is this an official Turno API?
No. Cotlet is independent and not affiliated with Turno. The endpoints you build run in your own signed-in Turno 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 Turno changes its screens?
An endpoint works while Turno works the way it did when you built it. If Turno 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 Turno 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.