Toast API · unofficial, by Cotlet
Create your own Toast API
Toast lets a restaurant create its own API credentials, but they are read only and need RMS Essentials or higher (checked 20 Nov 2026). With Cotlet you can build your own. Do a job once with your AI agent in your Toast 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 Toast 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 Toast. Toast is a trademark of its owner. If Toast's own integrations cover what you need, use them first.
curl -X POST "https://cotlet.dev/api/v1/custom/sales-by-server" \
-H "Authorization: Bearer $COTLET_API_KEY" \
-H "Content-Type: application/json" \
-d '{"date": "2026-11-19"}' const url = "https://cotlet.dev/api/v1/custom/sales-by-server";
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-19" }),
});
const { data } = await res.json(); import os
import requests
key = os.environ["COTLET_API_KEY"]
res = requests.post(
"https://cotlet.dev/api/v1/custom/sales-by-server",
headers={"Authorization": f"Bearer {key}"},
json={"date": "2026-11-19"},
)
data = res.json()["data"] {
"data": [
{
"server": "Jess M.",
"net_sales": "$1,840.00",
"voids": 1,
"tips": "$342.00"
},
{
"server": "Omar S.",
"net_sales": "$1,515.00",
"voids": 0,
"tips": "$288.00"
}
]
} 01 Build
How do you build a Toast endpoint with Cotlet?
-
Sign in to Toast 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 night's net sales, voids and tips for each server."
-
Save it as an endpoint.
Give it a name, choose its inputs, such as a date or a location, 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 Toast session.cotlet.dev/ api/ v1/ custom/ <name>
02 Endpoints
Example endpoints you could build for Toast
Cotlet ships no fixed list of Toast endpoints. You decide which endpoints you build and what each one returns.
-
POST
/api/v1/custom/sales-by-server Sales by server
Net sales, voids and tips for each server on a day
-
POST
/api/v1/custom/items-with-ingredient Items with an ingredient
Menu items whose name or description names it
-
POST
/api/v1/custom/open-time-entries Time entries without a clock-out
Employee, date and clock-in of each open entry
-
POST
/api/v1/custom/slow-items Slow items
Items sold fewer times than you set, for a period
-
POST
/api/v1/custom/writeseighty-six-item 86 an item
The menu item you name marked out of stock
A call to an endpoint you built could look like this:
curl -X POST "https://cotlet.dev/api/v1/custom/sales-by-server" \
-H "Authorization: Bearer $COTLET_API_KEY" \
-H "Content-Type: application/json" \
-d '{"date": "2026-11-19"}' The answer is JSON, with your fields under data:
{
"data": [
{
"server": "Jess M.",
"net_sales": "$1,840.00",
"voids": 1,
"tips": "$342.00"
},
{
"server": "Omar S.",
"net_sales": "$1,515.00",
"voids": 0,
"tips": "$288.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 Toast endpoints for?
- Schedule Cotlet endpoint Slack or email
A morning report in n8n or Make.
Last night's sales, voids and tips sent to Slack or email before the lunch shift.
- Kitchen form endpoint 86 list
An 86 from the kitchen.
The kitchen marks an ingredient as gone, and the items that use it come off the menu after your OK.
- Schedule endpoint Google Sheets
A labor sheet.
Time entries and labor cost pulled into Google Sheets every week.
- Voice agent endpoint 86 list
Your own AI phone assistant.
A voice agent that checks the 86 list before it tells a caller what is on tonight.
04 Access
What can an endpoint see and change?
An endpoint works in your own Toast session, so it can read and change only what your Toast 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 an item 86, 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 Toast have an official API?
Toast: a restaurant creates Standard API access credentials in Toast Web; they read only, and need RMS Essentials or higher and the Manage Integrations permission (checked 20 Nov 2026). Webhook subscriptions are made in Toast Web, and reports download as CSV or XLS. The full picture with sources: Does Toast have an API or MCP server?
Want ChatGPT or Claude to work in Toast instead of code? See the Toast 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.
Toast API with Cotlet: questions
Is this an official Toast API?
No. Cotlet is independent and not affiliated with Toast. The endpoints you build run in your own signed-in Toast 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 Toast changes its screens?
An endpoint works while Toast works the way it did when you built it. If Toast 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 Toast 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.