eDesk API · unofficial, by Cotlet
Create your own eDesk API
eDesk's API needs the Enterprise plan or higher (checked 20 Nov 2026). With Cotlet you can build your own. Do a job once with your AI agent in your eDesk 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 eDesk 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 eDesk. eDesk is a trademark of its owner. If eDesk's own integrations cover what you need, use them first.
curl -X POST "https://cotlet.dev/api/v1/custom/where-is-my-order-tickets" \
-H "Authorization: Bearer $COTLET_API_KEY" \
-H "Content-Type: application/json" \
-d '{"channel": "Amazon"}' const url = "https://cotlet.dev/api/v1/custom/where-is-my-order-tickets";
const res = await fetch(url, {
method: "POST",
headers: {
Authorization: `Bearer ${process.env.COTLET_API_KEY}`,
"Content-Type": "application/json",
},
body: JSON.stringify({ channel: "Amazon" }),
});
const { data } = await res.json(); import os
import requests
key = os.environ["COTLET_API_KEY"]
res = requests.post(
"https://cotlet.dev/api/v1/custom/where-is-my-order-tickets",
headers={"Authorization": f"Bearer {key}"},
json={"channel": "Amazon"},
)
data = res.json()["data"] {
"data": [
{
"ticket": "T-20418",
"order": "4471",
"buyer": "Dana R.",
"tracking": "in transit",
"waiting": "3h"
},
{
"ticket": "T-20431",
"order": "4938",
"buyer": "Mia K.",
"tracking": "no tracking",
"waiting": "1h"
}
]
} 01 Build
How do you build an eDesk endpoint with Cotlet?
-
Sign in to eDesk 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 open tickets that ask where an order is, with the order number, the buyer and the tracking status."
-
Save it as an endpoint.
Give it a name, choose its inputs, such as a channel or a tag, 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 eDesk session.cotlet.dev/ api/ v1/ custom/ <name>
02 Endpoints
Example endpoints you could build for eDesk
Cotlet ships no fixed list of eDesk endpoints. You decide which endpoints you build and what each one returns.
-
POST
/api/v1/custom/where-is-my-order-tickets Where-is-my-order tickets
Ticket, order, buyer and tracking status of each open delivery question
-
POST
/api/v1/custom/tickets-with-tag Tickets with a tag
Open and waiting tickets with the tag you name, newest first
-
POST
/api/v1/custom/order-for-ticket The order behind a ticket
Items, dispatch date and tracking of the order a ticket is about
-
POST
/api/v1/custom/returns-by-channel Returns by channel
Return and cancellation tickets for a period, counted per channel
-
POST
/api/v1/custom/writesadd-internal-note Add an internal note
A note on the ticket you name, seen only by your team
A call to an endpoint you built could look like this:
curl -X POST "https://cotlet.dev/api/v1/custom/where-is-my-order-tickets" \
-H "Authorization: Bearer $COTLET_API_KEY" \
-H "Content-Type: application/json" \
-d '{"channel": "Amazon"}' The answer is JSON, with your fields under data:
{
"data": [
{
"ticket": "T-20418",
"order": "4471",
"buyer": "Dana R.",
"tracking": "in transit",
"waiting": "3h"
},
{
"ticket": "T-20431",
"order": "4938",
"buyer": "Mia K.",
"tracking": "no tracking",
"waiting": "1h"
}
]
} 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 eDesk endpoints for?
- Schedule Cotlet endpoint Slack or email
A Monday returns report in n8n or Make.
Last week's return and cancellation tickets by channel, sent to Slack or email.
- Schedule endpoint Warehouse tool
Late orders for your warehouse.
Tickets about orders with no tracking, passed to the team that ships them.
- Schedule endpoint Google Sheets
A support dashboard.
Ticket counts by channel pulled into Google Sheets each week.
- Chat agent endpoint order
Your own AI assistant.
A chat agent that reads the order behind a ticket before it drafts an answer.
04 Access
What can an endpoint see and change?
An endpoint works in your own eDesk session, so it can read and change only what your eDesk 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 an internal 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 eDesk have an official API?
eDesk has a public API for tickets, messages, orders, contacts and tags, with API tokens an Admin creates, on the Enterprise plan or higher (checked 20 Nov 2026). Message Rules can call a webhook URL of your choice. The full picture with sources: Does eDesk have an API or MCP server?
Want ChatGPT or Claude to work in eDesk instead of code? See the eDesk 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.
eDesk API with Cotlet: questions
Is this an official eDesk API?
No. Cotlet is independent and not affiliated with eDesk. The endpoints you build run in your own signed-in eDesk 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 eDesk changes its screens?
An endpoint works while eDesk works the way it did when you built it. If eDesk 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 eDesk 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.