Deliverect API · unofficial, by Cotlet
Create your own Deliverect API
Deliverect: the API is for integration partners, onboarded and certified first; no API for your own account found (checked 20 Nov 2026). With Cotlet you can build your own. Do a job once with your AI agent in your Deliverect 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 Deliverect 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 Deliverect. Deliverect is a trademark of its owner. If Deliverect's own integrations cover what you need, use them first.
curl -X POST "https://cotlet.dev/api/v1/custom/failed-orders" \
-H "Authorization: Bearer $COTLET_API_KEY" \
-H "Content-Type: application/json" \
-d '{"date": "2026-11-19"}' const url = "https://cotlet.dev/api/v1/custom/failed-orders";
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/failed-orders",
headers={"Authorization": f"Bearer {key}"},
json={"date": "2026-11-19"},
)
data = res.json()["data"] {
"data": [
{
"time": "21:14",
"location": "Main Street",
"channel": "Delivery app A",
"reason": "Product not found in POS"
},
{
"time": "22:02",
"location": "Main Street",
"channel": "Delivery app B",
"reason": "POS offline"
}
]
} 01 Build
How do you build a Deliverect endpoint with Cotlet?
-
Sign in to Deliverect 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 orders that failed to reach the POS on a day, with time, location, channel and reason."
-
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 Deliverect session.cotlet.dev/ api/ v1/ custom/ <name>
02 Endpoints
Example endpoints you could build for Deliverect
Cotlet ships no fixed list of Deliverect endpoints. You decide which endpoints you build and what each one returns.
-
POST
/api/v1/custom/failed-orders Failed orders for a day
Time, location, channel and reason of each failed order
-
POST
/api/v1/custom/orders-by-channel Orders by channel
Order count and sales per channel for a period
-
POST
/api/v1/custom/snoozed-products Snoozed products
Products snoozed per location, with since when
-
POST
/api/v1/custom/opening-hours Opening hours
Hours per location and channel
-
POST
/api/v1/custom/writessnooze-product Snooze a product
The product you name, snoozed on every channel until a time you set
A call to an endpoint you built could look like this:
curl -X POST "https://cotlet.dev/api/v1/custom/failed-orders" \
-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": [
{
"time": "21:14",
"location": "Main Street",
"channel": "Delivery app A",
"reason": "Product not found in POS"
},
{
"time": "22:02",
"location": "Main Street",
"channel": "Delivery app B",
"reason": "POS offline"
}
]
} 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 Deliverect endpoints for?
- Schedule Cotlet endpoint Slack
A morning failed-orders report.
Last night's failed orders, sent to Slack before the lunch shift.
- Kitchen sheet endpoint snooze
Stock to snooze.
A sold-out item in your kitchen sheet snoozed on every channel.
- Daily endpoint Google Sheets
A channel dashboard.
Orders per channel pulled into Google Sheets or Looker Studio every day.
- Chat agent endpoint products
Your own operations assistant.
A chat agent that checks snoozed products before it answers a manager.
04 Access
What can an endpoint see and change?
An endpoint works in your own Deliverect session, so it can read and change only what your Deliverect 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 snoozing a product, 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 Deliverect have an official API?
Deliverect: the developer docs are for integration partners, who get production credentials after certification, and webhooks are for those integrations (checked 20 Nov 2026). Deliverect's official Claude connector reads your account and changes nothing. The full picture with sources: Does Deliverect have an API or MCP server?
Want ChatGPT or Claude to work in Deliverect instead of code? See the Deliverect 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.
Deliverect API with Cotlet: questions
Is this an official Deliverect API?
No. Cotlet is independent and not affiliated with Deliverect. The endpoints you build run in your own signed-in Deliverect 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 Deliverect changes its screens?
An endpoint works while Deliverect works the way it did when you built it. If Deliverect 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 Deliverect 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.