Allison API · unofficial, by Cotlet
Create your own Allison API
Allison: no public API found on getallison.com or in its help center (checked 20 Nov 2026). With Cotlet you can build your own. Do a job once with your AI agent in your Allison 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 Allison 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 Allison. Allison is a trademark of its owner. If Allison's own integrations cover what you need, use them first.
curl -X POST "https://cotlet.dev/api/v1/custom/cleans-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/cleans-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/cleans-for-day",
headers={"Authorization": f"Bearer {key}"},
json={"date": "2026-11-21"},
)
data = res.json()["data"] {
"data": [
{
"time": "08:00",
"customer": "Johnson home",
"address": "12 Oak St",
"service": "Recurring clean",
"cleaner": "Rosa"
},
{
"time": "10:30",
"customer": "Tom H.",
"address": "48 Elm Ave",
"service": "Deep clean",
"cleaner": "Rosa"
}
]
} 01 Build
How do you build an Allison endpoint with Cotlet?
-
Sign in to Allison 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 cleans with time, customer, address, service and cleaner."
-
Save it as an endpoint.
Give it a name, choose its inputs, such as a date or a cleaner, 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 Allison session.cotlet.dev/ api/ v1/ custom/ <name>
02 Endpoints
Example endpoints you could build for Allison
Cotlet ships no fixed list of Allison endpoints. You decide which endpoints you build and what each one returns.
-
POST
/api/v1/custom/cleans-for-day Cleans for a day
Time, customer, address, service and cleaner of each clean
-
POST
/api/v1/custom/jobs-without-cleaner Jobs with no cleaner
Jobs in a period that nobody is assigned to
-
POST
/api/v1/custom/unpaid-invoices Unpaid invoices
Customer, amount and date of each unpaid invoice
-
POST
/api/v1/custom/open-quotes Open quotes
Quotes sent and not yet booked, with the date sent
-
POST
/api/v1/custom/writesadd-customer-note Add a note to a customer
A note on the customer you name
A call to an endpoint you built could look like this:
curl -X POST "https://cotlet.dev/api/v1/custom/cleans-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": "08:00",
"customer": "Johnson home",
"address": "12 Oak St",
"service": "Recurring clean",
"cleaner": "Rosa"
},
{
"time": "10:30",
"customer": "Tom H.",
"address": "48 Elm Ave",
"service": "Deep clean",
"cleaner": "Rosa"
}
]
} 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 Allison endpoints for?
- Schedule Cotlet endpoint Slack or email
A route sheet each evening.
Tomorrow's cleans by cleaner, sent to your team in Slack or by email.
- Monday endpoint Google Sheets
A collections list.
Unpaid invoices pulled into Google Sheets every Monday.
- Sunday endpoint Team chat
Gaps in next week.
Jobs with no cleaner, posted to your team chat on Sunday.
- Voice or chat agent endpoint schedule
Your own AI receptionist.
A voice or chat agent that checks the schedule before it offers a time.
04 Access
What can an endpoint see and change?
An endpoint works in your own Allison session, so it can read and change only what your Allison 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 adding a customer note, 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 Allison have an official API?
Allison: no public API, developer docs or webhooks found on getallison.com or in its help center (checked 20 Nov 2026). Allison has an official MCP server for the account owner, read only per its help center, and a Zapier integration in beta. The full picture with sources: Does Allison have an API or MCP server?
Want ChatGPT or Claude to work in Allison instead of code? See the Allison 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.
Allison API with Cotlet: questions
Is this an official Allison API?
No. Cotlet is independent and not affiliated with Allison. The endpoints you build run in your own signed-in Allison 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 Allison changes its screens?
An endpoint works while Allison works the way it did when you built it. If Allison 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 Allison 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.