ResDiary API · unofficial, by Cotlet
Create your own ResDiary API
ResDiary documents its API for integration partners, with credentials after a written agreement (checked 20 Nov 2026). With Cotlet you can build your own. Do a job once with your AI agent in your ResDiary 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 ResDiary 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 ResDiary. ResDiary is a trademark of its owner. If ResDiary's own integrations cover what you need, use them first.
curl -X POST "https://cotlet.dev/api/v1/custom/bookings-for-date" \
-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-date";
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-date",
headers={"Authorization": f"Bearer {key}"},
json={"date": "2026-11-21"},
)
data = res.json()["data"] {
"data": [
{
"time": "19:00",
"guest": "Okafor",
"covers": 4,
"table": "T9",
"notes": "nut allergy"
},
{
"time": "20:15",
"guest": "Moreau",
"covers": 6,
"table": "T12",
"notes": "birthday"
}
]
} 01 Build
How do you build a ResDiary endpoint with Cotlet?
-
Sign in to ResDiary 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 bookings for a date with time, guest, covers, table and notes."
-
Save it as an endpoint.
Give it a name, choose its inputs, such as a date or an area, 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 ResDiary session.cotlet.dev/ api/ v1/ custom/ <name>
02 Endpoints
Example endpoints you could build for ResDiary
Cotlet ships no fixed list of ResDiary endpoints. You decide which endpoints you build and what each one returns.
-
POST
/api/v1/custom/bookings-for-date Bookings for a date
Time, guest, covers, table and notes for each booking
-
POST
/api/v1/custom/free-tables Free tables
Tables free for a party size at the time you name
-
POST
/api/v1/custom/guest-history Guest history
A guest's past visits, covers and notes
-
POST
/api/v1/custom/no-shows No-shows for a period
Guest, date and party size of each no-show
-
POST
/api/v1/custom/writesadd-booking-note Add a note to a booking
A note saved on the booking you name
A call to an endpoint you built could look like this:
curl -X POST "https://cotlet.dev/api/v1/custom/bookings-for-date" \
-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": "19:00",
"guest": "Okafor",
"covers": 4,
"table": "T9",
"notes": "nut allergy"
},
{
"time": "20:15",
"guest": "Moreau",
"covers": 6,
"table": "T12",
"notes": "birthday"
}
]
} 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 ResDiary endpoints for?
- Schedule Cotlet endpoint Slack or email
A kitchen brief in n8n or Make.
Tonight's bookings with allergy notes, sent to Slack or email at 4 pm.
- Schedule endpoint Google Sheets
A weekly numbers sheet.
Covers and no-shows pulled every Monday into Google Sheets.
- Voice or chat agent endpoint free tables
Your own AI receptionist.
A voice or chat agent that checks free tables before it offers a time.
- After a visit endpoint CRM
Your CRM.
A guest's visit history added to your CRM after each visit.
04 Access
What can an endpoint see and change?
An endpoint works in your own ResDiary session, so it can read and change only what your ResDiary 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 note to a booking, 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 ResDiary have an official API?
ResDiary's API documentation is written for integration partners and third-party applications. Its API License Terms give credentials only after the Permitted Purpose and a Data Flow Diagram are agreed in writing (checked 20 Nov 2026). The full picture with sources: Does ResDiary have an API or MCP server?
Want ChatGPT or Claude to work in ResDiary instead of code? See the ResDiary 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.
ResDiary API with Cotlet: questions
Is this an official ResDiary API?
No. Cotlet is independent and not affiliated with ResDiary. The endpoints you build run in your own signed-in ResDiary 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 ResDiary changes its screens?
An endpoint works while ResDiary works the way it did when you built it. If ResDiary 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 ResDiary 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.