[Cotlet](https://cotlet.dev/index.md) · [Integrations](https://cotlet.dev/integrations.md) · [How it works](https://cotlet.dev/how-it-works.md) · [Use cases](https://cotlet.dev/use-cases.md) · [Security](https://cotlet.dev/security.md) · [For developers](https://cotlet.dev/for-developers.md) · [For automation agencies](https://cotlet.dev/for-agencies.md) · [Blog](https://cotlet.dev/blog.md) · [API docs](https://cotlet.dev/docs.md) · [Help center](https://cotlet.dev/help.md) · [Changelog](https://cotlet.dev/changelog.md) · [Contact](https://cotlet.dev/contact.md) · [Pricing](https://cotlet.dev/pricing.md) · [Sign up](https://cotlet.dev/signup)

# eDesk API and MCP server

> eDesk has a full REST API but no MCP server (checked 20 Oct 2026). Its docs and help center list none. The API needs the Enterprise plan, and an Admin has to create the API token under Settings > API Tokens. So on any other plan there is no API at all.

Helpdesk for online sellers: customer messages from Amazon, eBay, Shopify and other marketplaces and webstores in one Mailbox, with orders and tracking beside each ticket, templates and Message Rules.

## What is the eDesk API?

Cotlet's eDesk API exposes 11 endpoints for your own eDesk account: list tickets, get ticket, list orders, get order, list templates, list users, list tags, list channels, reply to ticket, add internal note and update ticket. The list_tickets endpoint returns tickets in the Mailbox by section, channel, type, owner or tag, with status, order number and reply count. Each endpoint takes simple JSON inputs like query, ticket_id or status and works both as an operation of the edesk_read or edesk_write MCP tool for agents and as a REST call for scripts.

- **Category:** [Customer support](https://cotlet.dev/integrations/category/customer-support.md)
- **Endpoints:** 11 (8 read, 3 write)
- **Updated:** 2026-10-21

eDesk has a full REST API but no MCP server (checked 20 Oct 2026). Cotlet is a hosted MCP server and REST API for eDesk with 11 endpoints (8 read, 3 write): you sign in once in your own cloud browser, your AI agent does the work.

## Does eDesk have an official API?

eDesk has a full REST API but no MCP server (checked 20 Oct 2026). Its docs and help center list none. The API needs the Enterprise plan, and an Admin has to create the API token under Settings > API Tokens. So on any other plan there is no API at all.

| Task | eDesk official | Cotlet |
|---|---|---|
| Read tickets and their messages | Yes: REST API on the Enterprise plan, token from an Admin | Yes |
| Reply to a customer | Yes: Create Message with send; delivery is queued, and Mirakl channels need a default recipients setting | Yes |
| Add an internal note | Yes: Create Message with type Note | Yes |
| Set owner, tags and status | Yes: Update Ticket, Enterprise plan | Yes |
| Read orders and tracking | Yes: Sales Orders endpoints, Enterprise plan | Yes |
| Read reply templates | Yes: List Templates, Enterprise plan | Yes |
| Search tickets by customer or order keyword | Partly: List Tickets filters by IDs, status, type, dates and seller order ID, with no free-text search | Yes |
| Snooze a ticket or mention a teammate | No | Yes |

Sources: [eDesk Help: Getting started with the eDesk API](https://support.edesk.com/getting-started-with-the-edesk-api), [eDesk Help: How to generate a token for the eDesk API](https://support.edesk.com/how-to-generate-a-token-edesk-api), [eDesk developers: API reference](https://developers.edesk.com/reference/listtickets), [eDesk developers: Create Message](https://developers.edesk.com/reference/createmessage)

## For AI agents

```text
eDesk has a full REST API but no MCP server (checked 20 Oct 2026). Its docs and help center list none. The API needs the Enterprise plan, and an Admin has to create the API token under Settings > API Tokens. So on any other plan there is no API at all.
Cotlet provides a hosted MCP server and REST API for eDesk: 11 tools (8 read, 3 write).
Access       Sign up at https://cotlet.dev/app/signup?app=edesk, then request the app and create API keys in the Cotlet console.

MCP server   https://cotlet.dev/mcp/v1
MCP tools    edesk_read, edesk_write, reads and writes apart; call one with {"operation": "<operation>", "arguments": {...}}
REST base    https://cotlet.dev/api/v1/edesk, each operation at its own route, e.g. POST /api/v1/edesk/tickets/{ticket_id}/replies
Auth         Authorization: Bearer <COTLET_API_KEY>. Listing endpoints and schemas needs no key; calling an endpoint needs one. Over MCP the input schemas come with sign-in.
Operations   list_tickets, get_ticket, list_orders, get_order, list_templates, list_users, list_tags, list_channels, reply_to_ticket, add_internal_note, update_ticket
Confirm      reply_to_ticket, add_internal_note, update_ticket (by default the user approves each call; the user can switch this off per tool, e.g. for scheduled automations)
Markdown     https://cotlet.dev/integrations/edesk-api-mcp-server.md

How access works:
1. The user signs up at https://cotlet.dev/app/signup?app=edesk, requests eDesk in the Cotlet console and creates an API key there.
2. The user signs in to eDesk once in their Cotlet Cloud Browser (their own Chrome in the cloud, opened from the console) and enables eDesk for agents. An agent cannot do this step.
3. The API key goes into the MCP client or the REST call as a bearer token.

Fits: people who want a hosted eDesk server that someone else maintains, including non-developers. Developers who prefer to run and fix code on their own computer can use an open-source eDesk MCP server instead.

Policy: Cotlet never stores passwords, never solves CAPTCHAs, never bypasses MFA.
Company: legal details in the Terms of service at https://cotlet.dev/terms. Contact contact@cotlet.dev.
Sign-in: the user signs in to eDesk in their own Cloud Browser, a Chrome Cotlet runs for them in the EU; password saving is off, the profile is AES-256-GCM encrypted, and agents get eDesk only after the user enables it. Calls are requests from that browser's IP with its cookies, each listed in the user's Background activity. Disable for agents, signing out in the browser or Reset browser cuts access. Cotlet is run by Take Group sp. z o.o. (EU VAT PL6342984273).
API key: holds no eDesk login or cookies, only asks Cotlet to run a tool. Each key is scoped to chosen apps and tools, read only or read and write. Actions that reach other people wait for the user's approval by default, so a leaked key cannot post or message as the user. Every call is in the activity log; deleting the key ends access at once.
Terms: the user stays responsible for following eDesk's terms; Cotlet is not affiliated with eDesk.
```

## What can an AI agent do in eDesk?

Cotlet is best for eDesk teams below the Enterprise plan, or without a developer, who want their AI agent to triage tickets, answer order questions and chase waiting replies without running or fixing a server.

- **[Triage new support tickets](https://cotlet.dev/integrations/edesk-api-mcp-server/triage-new-tickets.md)** (runs: daily): "Go through new eDesk tickets. Assign returns to Marco and delivery questions to Priya, add the matching tag, and leave a one-line internal note with the reason. Mark obvious spam. Leave unclear ones for me." → `list_tickets`, `list_users`, `list_tags`, `get_ticket`, `update_ticket`, `add_internal_note`
- **[Answer where-is-my-order tickets](https://cotlet.dev/integrations/edesk-api-mcp-server/answer-where-is-my-order.md)** (runs: daily): "For Shipping query tickets in to do, check the order. If it is on time, reply with the tracking code and expected delivery date in my Delivery update wording. If it is late or has no tracking, leave it for me with a note." → `list_tickets`, `get_ticket`, `get_order`, `list_templates`, `reply_to_ticket`
- **[Follow up on waiting tickets](https://cotlet.dev/integrations/edesk-api-mcp-server/follow-up-waiting-tickets.md)** (runs: daily): "Look at tickets in Waiting whose last message is older than 7 days. If the customer never answered my question, send a short reminder and keep it waiting. If I already reminded them once, mark the ticket resolved." → `list_tickets`, `get_ticket`, `reply_to_ticket`, `update_ticket`
- **Weekly returns and cancellations digest** (runs: weekly): "Every Monday, list last week's Return request and Cancellation tickets by channel, with the order number and the ticket status." → `list_tickets`, `list_channels`, `get_order`
- **Flag negative feedback for a manager**: "Find new Negative feedback tickets, add a note with the order and what the buyer complained about, and mention Priya on each." → `list_tickets`, `get_ticket`, `add_internal_note`, `update_ticket`

## Can eDesk automations run on a schedule in n8n, Make or Zapier?

Yes. Cotlet does not replace your automation platform: it gives it a eDesk connection it does not have, with the same API key as your agent. Write actions ask for your OK by default; switch that off in your dashboard for the tools you choose, for example to triage new support tickets, and the schedule runs on its own. Cotlet runs in the cloud, so it keeps going while your computer is off.

| Where | How to connect | How to schedule |
|---|---|---|
| Your AI agent | Add https://cotlet.dev/mcp/v1 with your API key. | A scheduled agent run, for example a Claude Code routine. |
| n8n | MCP Client node with https://cotlet.dev/mcp/v1, or an HTTP Request node with the endpoint's method and URL, such as GET https://cotlet.dev/api/v1/edesk/tickets. | Schedule Trigger node. |
| Make | HTTP module: the endpoint's method and URL with an Authorization: Bearer header, and a JSON body for POST, PUT and PATCH. | Scenario schedule. |
| Zapier | Webhooks by Zapier, Custom Request: the same method, URL, header and body. | Schedule by Zapier trigger. |
| Your own script | GET https://cotlet.dev/api/v1/edesk/tickets with your API key. | cron or GitHub Actions. |

## Tools

**For AI agents:** Every endpoint and its schema is public. The 11 endpoints on this page, with parameters and example responses, can be listed without an account. Calling one returns 401 without an API key and 403 while the key has no access to eDesk.

### list_tickets

Tickets in the Mailbox by section, channel, type, owner or tag, with status, order number and reply count. Access: read. REST: `GET /api/v1/edesk/tickets`. MCP: `edesk_read → list_tickets`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `status` | enum | no | new, to_do, waiting, snoozed, resolved or spam. Default: to_do. |
| `query` | string | no | Search text: customer name, email, phone, product name, SKU or order ID. |
| `type` | string | no | Ticket type as eDesk names it, for example Shipping query, Return request, Cancellation, Negative feedback. |
| `channel_id` | integer | no | Channel ID from list_channels. |
| `owner_id` | integer | no | User ID from list_users. Only tickets owned by this user. |
| `tag` | string | no | Only tickets with this tag. |
| `updated_before` | date | no | Only tickets whose latest message is before this date (YYYY-MM-DD). |
| `limit` | integer | no | How many items to return per page. |
| `cursor` | string | no | Next page cursor from the previous call. |

Lists tickets the way the Mailbox shows them. status picks the section: new (never answered), to_do, waiting, snoozed, resolved or spam. query searches customer details (name, email, phone) and order details (product name, SKU, order ID) like the Search bar. type is the ticket type as eDesk names it, for example Shipping query, Return request, Cancellation or Negative feedback. last_updated_at is the time of the latest message on the ticket. Pass next_cursor back as cursor for the next page. Use ticket_id with get_ticket, reply_to_ticket and update_ticket.

Example response:

```json
{
  "tickets": [
    {
      "ticket_id": 48199,
      "subject": "Parcel has not arrived",
      "status": "waiting",
      "type": "Shipping query",
      "channel": "Amazon UK - Brightside Home",
      "customer": "Emma Wright",
      "owner": null,
      "tags": [],
      "replies": 1,
      "order_number": "026-3350917-1184029",
      "last_updated_at": "2026-10-12 08:15:00"
    },
    {
      "ticket_id": 48177,
      "subject": "Item arrived with a cracked lid",
      "status": "waiting",
      "type": "Return request",
      "channel": "eBay UK - Brightside Home",
      "customer": "Tom Hale",
      "owner": "Marco Silva",
      "tags": [
        "Returns"
      ],
      "replies": 2,
      "order_number": "15-11874-62103",
      "last_updated_at": "2026-10-11 16:40:00"
    }
  ],
  "next_cursor": null
}
```

### get_ticket

One ticket with its messages and internal notes, customer, tags and the order panel with tracking. Access: read. REST: `GET /api/v1/edesk/tickets/{ticket_id}`. MCP: `edesk_read → get_ticket`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `ticket_id` | integer | yes | Ticket ID from list_tickets, the number eDesk shows as Ticket ID. |

Returns one ticket as the ticket view shows it: status, type, channel, owner, tags, the customer and every message and internal note in order, oldest first. kind is message for what the customer wrote, reply for what your team sent and note for an internal note. order is the order eDesk linked to the ticket, with shipping status, tracking code and carrier when eDesk has them, and the estimated delivery. order is null when eDesk found no match; use list_orders to look it up.

Example response:

```json
{
  "ticket_id": 48210,
  "subject": "Where is my parcel?",
  "status": "to_do",
  "type": "Shipping query",
  "channel": "Amazon UK - Brightside Home",
  "owner": null,
  "tags": [],
  "customer": {
    "name": "Emma Wright",
    "email": "emma.wright@example.com"
  },
  "order": {
    "order_id": 90412,
    "order_number": "203-7718305-2294466",
    "status": "In transit",
    "shipped_at": "2026-10-09",
    "expected_delivery_to": "2026-10-14",
    "tracking": {
      "code": "HB204418830GB",
      "carrier": "Royal Mail"
    }
  },
  "messages": [
    {
      "message_id": 771204,
      "kind": "message",
      "created_at": "2026-10-12 08:15:00",
      "body": "It was due on Saturday and nothing has arrived. Where is my parcel?"
    }
  ]
}
```

### list_orders

Orders from the All Orders page, filtered by search text, status, channel or date, with items and ticket link. Access: read. REST: `GET /api/v1/edesk/orders`. MCP: `edesk_read → list_orders`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `query` | string | no | Order number, customer name or email, product name or SKU. |
| `status` | string | no | Order status as eDesk shows it, for example Order Shipped. |
| `channel_id` | integer | no | Channel ID from list_channels. |
| `since` | date | no | Only orders placed on or after this date (YYYY-MM-DD). |
| `limit` | integer | no | How many items to return per page. |
| `cursor` | string | no | Next page cursor from the previous call. |

Lists orders the way All Orders shows them, newest first. query matches the order number, customer details, product name or SKU. status is the order status as eDesk shows it, for example Order Shipped. ticket_id is set when the order is linked to a ticket. Use order_id with get_order. Pass next_cursor back as cursor for the next page.

Example response:

```json
{
  "orders": [
    {
      "order_id": 90412,
      "order_number": "203-7718305-2294466",
      "channel": "Amazon UK - Brightside Home",
      "status": "In transit",
      "ordered_at": "2026-10-08",
      "shipped_at": "2026-10-09",
      "total": "GBP 84.90",
      "items": [
        {
          "sku": "BH-KETTLE-1L",
          "product": "Glass kettle 1 L",
          "quantity": 1
        }
      ],
      "ticket_id": 48210
    }
  ],
  "next_cursor": null
}
```

### get_order

One order with items, status, dates, delivery address, tracking code and carrier. Access: read. REST: `GET /api/v1/edesk/orders/{order_id}`. MCP: `edesk_read → get_order`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `order_id` | integer | yes | Order ID from list_orders or get_ticket. |

Returns the order as the Order information panel shows it: order number, date ordered, shipping status, tracking code, tracking link and carrier when eDesk has them, estimated delivery dates, the delivery address, the products and the cost. ticket_id is the linked ticket, or null. A marketplace can hide buyer details, so ship_to may be thin on some channels.

Example response:

```json
{
  "order_id": 90412,
  "order_number": "203-7718305-2294466",
  "channel": "Amazon UK - Brightside Home",
  "status": "In transit",
  "ordered_at": "2026-10-08",
  "shipped_at": "2026-10-09",
  "expected_delivery_from": "2026-10-12",
  "expected_delivery_to": "2026-10-14",
  "tracking": {
    "code": "HB204418830GB",
    "carrier": "Royal Mail",
    "link": "https://tracking.example.com/HB204418830GB"
  },
  "items": [
    {
      "sku": "BH-KETTLE-1L",
      "product": "Glass kettle 1 L",
      "quantity": 1,
      "price": 79.9
    }
  ],
  "shipping": 5,
  "total": 84.9,
  "currency": "GBP",
  "ship_to": {
    "city": "Leeds",
    "country": "United Kingdom"
  },
  "ticket_id": 48210
}
```

### list_templates

Reply templates from Settings, Smart Tools, Templates, with text and usage. Access: read. REST: `GET /api/v1/edesk/templates`. MCP: `edesk_read → list_templates`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `query` | string | no | Only templates whose name contains this text. |

Lists the templates your account has, from Settings > Smart Tools > Templates. body is the template text with snippets left as written, for example #order_number# and #tracking_code#, so the agent fills them from get_order. Inactive templates are not returned. Templates are read only here: Cotlet does not create or change them.

Example response:

```json
{
  "templates": [
    {
      "template_id": 512,
      "name": "Delivery update",
      "subject": null,
      "body": "Hi #consumer_firstname#, your order #order_number# was dispatched on #dispatched_on#. Tracking code: #tracking_code#.",
      "type": "Consumer"
    }
  ]
}
```

### list_users

Teammates of your eDesk account with their role. Access: read. REST: `GET /api/v1/edesk/users`. MCP: `edesk_read → list_users`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `query` | string | no | Only users whose name or email contains this text. |

Lists the users of the account with user_id, name and role (Owner, Admin, Team Leader, Agent or a custom role). Use user_id as owner_id or mention_user_id in update_ticket. A ticket has one owner at a time.

Example response:

```json
{
  "users": [
    {
      "user_id": 3105,
      "name": "Marco Silva",
      "role": "Agent"
    },
    {
      "user_id": 3102,
      "name": "Priya Nair",
      "role": "Team Leader"
    }
  ]
}
```

### list_tags

Tags and tag groups in your eDesk account. Access: read. REST: `GET /api/v1/edesk/tags`. MCP: `edesk_read → list_tags`.

No parameters.

Lists the tags you can add to a ticket, each with its tag group. Pass tag names to add_tags of update_ticket exactly as listed. A user without permission to manage tags can still add them to tickets.

Example response:

```json
{
  "tags": [
    {
      "tag_id": 71,
      "name": "Returns",
      "group": "Topic"
    },
    {
      "tag_id": 72,
      "name": "Delivery",
      "group": "Topic"
    },
    {
      "tag_id": 73,
      "name": "VIP",
      "group": "Customer"
    }
  ]
}
```

### list_channels

Channels connected to eDesk: marketplaces, webstores and email. Access: read. REST: `GET /api/v1/edesk/channels`. MCP: `edesk_read → list_channels`.

No parameters.

Lists the channels from Settings > Mailbox > Channels with channel_id, name and marketplace. Use channel_id as a filter in list_tickets and list_orders.

Example response:

```json
{
  "channels": [
    {
      "channel_id": 14,
      "name": "Amazon UK - Brightside Home",
      "marketplace": "Amazon"
    },
    {
      "channel_id": 15,
      "name": "eBay UK - Brightside Home",
      "marketplace": "eBay"
    },
    {
      "channel_id": 21,
      "name": "Support email",
      "marketplace": "Email"
    }
  ]
}
```

### reply_to_ticket

Send a reply to the customer from the ticket, with the send status you choose. Access: write, asks the user first. REST: `POST /api/v1/edesk/tickets/{ticket_id}/replies`. MCP: `edesk_write → reply_to_ticket`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `ticket_id` | integer | yes | Ticket ID from list_tickets, the number eDesk shows as Ticket ID. |
| `body` | string | yes | Reply text, sent to the customer. |
| `send_status` | enum | no | to_do, waiting or resolved. Default: your eDesk send status setting. |

Types a reply in the Reply box of the ticket and clicks Send. The customer gets it on the channel the ticket came from, for example the marketplace messaging or email. send_status is the status the ticket takes after sending: to_do, waiting or resolved. Without it eDesk applies your user setting, and a customer reply reopens a resolved ticket. The tool sends plain text and does not fill snippets, so write the final text. Cotlet has no tool to unsend a message. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "message_id": 771209,
  "ticket_id": 48210,
  "kind": "reply",
  "status": "waiting",
  "sent_at": "2026-10-20 09:05:00"
}
```

### add_internal_note

Add a note to the ticket that only your teammates see. Access: write, asks the user first. REST: `POST /api/v1/edesk/tickets/{ticket_id}/internal-notes`. MCP: `edesk_write → add_internal_note`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `ticket_id` | integer | yes | Ticket ID from list_tickets, the number eDesk shows as Ticket ID. |
| `body` | string | yes | Note text, visible to your team only. |

Writes in the Note tab of the Reply box. The customer never sees a note, and teammates see it in the ticket thread. The note stays on the ticket and Cotlet has no tool to remove it. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "message_id": 771210,
  "ticket_id": 48212,
  "kind": "note",
  "created_at": "2026-10-20 09:07:00"
}
```

### update_ticket

Set owner, tags and status, snooze the ticket or mention a teammate. Access: write, asks the user first. REST: `PATCH /api/v1/edesk/tickets/{ticket_id}`. MCP: `edesk_write → update_ticket`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `ticket_id` | integer | yes | Ticket ID from list_tickets, the number eDesk shows as Ticket ID. |
| `status` | enum | no | to_do, waiting, resolved or spam. |
| `owner_id` | integer | no | User ID from list_users. |
| `add_tags` | string[] | no | Tag names from list_tags to add, keeping the existing ones. |
| `mention_user_id` | integer | no | User ID from list_users to mention on the ticket. |
| `snooze_until` | datetime | no | Snooze the ticket until this time (ISO 8601). |

Changes the ticket options. owner_id assigns the one owner a ticket can have and replaces the current one. add_tags adds tags and keeps the existing ones. status moves the ticket to to_do, waiting, resolved or spam. snooze_until hides the ticket from New and To Do until that time, then it returns to where it was. mention_user_id tags a teammate without changing the owner, and the ticket shows in their Mentioned section. Only the fields you pass change. Assigning and mentioning notify teammates, and resolving a ticket takes it off the queue. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "ticket_id": 48212,
  "status": "to_do",
  "owner": {
    "user_id": 3105,
    "name": "Marco Silva"
  },
  "tags": [
    "Returns"
  ],
  "mentioned": [],
  "snoozed_until": null
}
```

## How do I connect eDesk to Claude Code, Codex or Cursor?

Connecting eDesk takes three steps: sign up, sign in to eDesk once in your Cloud Browser and enable it for agents, then add one MCP server or call the REST API with the same key.

### Connect eDesk to your agent.

1. **Create an account** Sign up and add eDesk in the console. Your API key is there too.

2. **Sign in to eDesk in your Cloud Browser** Open your Cloud Browser in the console: your own Chrome in the cloud. Sign in to eDesk there yourself, the way you always do, then press Enable for agents, read only or read and write. We never save your password, and your agent keeps working even when your computer is off.

3. **Add Cotlet to your agent** Paste the snippet for your client. The same server and key serve every app you connect, so you do this once.

   Claude Code:

```
claude mcp add --transport http cotlet \
  https://cotlet.dev/mcp/v1 \
  --header "Authorization: Bearer $COTLET_API_KEY"
```

   Cursor:

```
{
  "mcpServers": {
    "cotlet": {
      "url": "https://cotlet.dev/mcp/v1",
      "headers": {
        "Authorization": "Bearer ${COTLET_API_KEY}"
      }
    }
  }
}
```

   Codex:

```
# ~/.codex/config.toml
[mcp_servers.cotlet]
url = "https://cotlet.dev/mcp/v1"
bearer_token_env_var = "COTLET_API_KEY"
```

4. **Ask your agent** Ask in plain words. Your agent finds the eDesk tools on the server and calls them for you; anything that reaches other people waits for your OK unless you switch that off for a tool.

```
Go through new eDesk tickets. Assign returns to Marco and delivery questions to Priya, add the matching tag, and leave a one-line internal note with the reason. Mark obvious spam. Leave unclear ones for me.
```

### Call eDesk from your scripts.

1. **Export your API key** Your scripts use the same API key as your agent. Keep it in an environment variable, never in your code.

```
export COTLET_API_KEY="cotlet_..."
```

2. **Call a tool** Every tool is an endpoint under /api/v1/edesk with its own method and path, listed with the endpoints above. Path parameters go in the URL; the other parameters go in the query for GET and DELETE and in a JSON body otherwise.

```
curl -X POST https://cotlet.dev/api/v1/edesk/tickets/48210/replies \
  -H "Authorization: Bearer $COTLET_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"body":"Hi Emma, your order 203-7718305-2294466 was dispatched on 9 October with Royal Mail. Tracking code: HB204418830GB. It should reach you by 14 October. Reply here if it has not arrived by then.","send_status":"waiting"}'
```

3. **Read the result** You get plain JSON back, ready for your script. A failed call costs nothing.

```
{
  "message_id": 771209,
  "ticket_id": 48210,
  "kind": "reply",
  "status": "waiting",
  "sent_at": "2026-10-20 09:05:00"
}
```

## Why use Cotlet for eDesk?

**Built for agents**

- One MCP server for every app you connect.
- The same tools as a REST API for scripts and cron jobs.
- Works with Claude Code, Codex and Cursor.

**Your login stays yours**

- You sign in to eDesk yourself, in your own Cloud Browser. We never save your password; the profile is encrypted with AES-256-GCM, the cipher 1Password uses.
- A+ on Qualys SSL Labs, securityheaders.com and Mozilla Observatory.
- The model never sees a login.
- No stored passwords, no CAPTCHA solving, no MFA bypass.

**You stay in control**

- Scope each API key: its apps, its tools, read only or read and write.
- Anything that reaches other people waits for your OK, so a leaked key cannot post or message as you.
- Every background request listed in your Background activity. Disable for agents in one click.

**Kept working for you**

- We test every integration every 6 hours.
- When eDesk changes, the tool pauses until we fix it.
- Failed calls cost nothing.

## Is it safe to connect eDesk to Cotlet?

Yes. You sign in to eDesk yourself, in your own Cloud Browser, and we never save your password. Your agents only get eDesk once you enable it, and every background request is listed. The browser profile is stored encrypted with AES-256-GCM, the same cipher 1Password uses for its vaults and Apple for iCloud Keychain. Independent public scanners grade cotlet.dev A+ and find it clean; click a result to rerun it yourself.

- **A+ on Qualys SSL Labs**: Encryption in transit: TLS setup and certificates, on all four server addresses. [Live result](https://www.ssllabs.com/ssltest/analyze.html?d=cotlet.dev)
- **A+ on securityheaders.com**: Browser protections sent with every page, all six headers present. [Live result](https://securityheaders.com/?q=cotlet.dev&followRedirects=on)
- **A+ on Mozilla Observatory**: Mozilla's web security baseline: score 120 of 100, 12 of 12 tests passed. [Live result](https://developer.mozilla.org/en-US/observatory/analyze?host=cotlet.dev)
- **Clean on Sucuri SiteCheck**: No malware, spam or defacement, and not on any of 9 blocklists, Google Safe Browsing included. [Live result](https://sitecheck.sucuri.net/results/cotlet.dev)

[How Cotlet protects your access](https://cotlet.dev/security.md)

### Common concerns

**Who runs Cotlet?**

Cotlet is run by Take Group, a Polish software company working since 2019. Take Group runs about 3,200 websites on its own systems and has its own DevOps team for infrastructure security. We built and used integrations like this inside the company for years before opening them as Cotlet.

**Is this an official eDesk integration?**

No, Cotlet is independent of eDesk. eDesk's own API is too limited for this work. Cotlet works through your own eDesk account, the way you use eDesk in the browser, so you need no partner approval and no developer setup.

**What about client data and GDPR?**

Cotlet is run from the EU and follows the GDPR. Cloud Browsers run in Finland, a Tier 1 country in the ITU Global Cybersecurity Index 2024. Data passes through a call and is not kept after it.

**Can I start with read only?**

Yes. Enable the app for agents as read only, or make the API key read only, and anything that reaches other people waits for your OK unless you switch that off per tool.

**Is it reliable?**

Every Cotlet service is checked every 3 minutes from Europe, North America, Asia and Australia. The live results and any outage are public at status.cotlet.dev.

**How do I stop?**

Press Disable for agents next to eDesk in your console: your agents lose access at once and you stay signed in. Signing out of eDesk in the browser works too, and Reset browser deletes the whole profile.

## Is there a eDesk MCP server on GitHub?

Yes. Community eDesk MCP servers exist, usually maintained by one person. Each one wraps the REST API, so it needs an API token, and that needs the Enterprise plan. You install and fix it yourself. Cotlet hosts the same kind of server for you, works in your signed-in eDesk session on your plan, and our team keeps it working.

|  | GitHub MCP server | Cotlet |
|---|---|---|
| Setup | Ask an Admin for an API token on the Enterprise plan, install the server, add it to each MCP client | Sign up, sign in to eDesk once, add one MCP server or API key |
| When eDesk changes | It breaks until you or the maintainer fix it | Our team tests it daily and fixes it for you; failed calls are free |
| Your eDesk access | An API token in a file on your computer, readable by any program you run | Signed in inside your own Cloud Browser in the EU, profile encrypted, only for the apps you enable, disabled for agents in one click |
| When access expires | Tokens expire (90 days by default) and tools fail until an Admin makes a new one | Your Cloud Browser keeps you signed in; if eDesk logs you out, your agent gets a link to sign in again |
| Upkeep | You update, monitor and debug it yourself | Nothing to host or update |
| Where it runs | Your computer, while it is on | Hosted: Claude Code, Codex, Cursor, n8n and scripts, also on a schedule |
| Price | Free, paid for with your time, plus the Enterprise plan | Free 7-day trial, then pay-as-you-go credit packs, no subscription |

### Which one fits you

**Pick Cotlet if**

- you are not a developer, or you do not want to maintain a server
- you need it to keep working when eDesk changes, without checking it yourself
- your agent or a script should run it on a schedule, also while your computer is off

**Pick an open-source server if**

- you are comfortable installing, updating and fixing it yourself
- you want your sign-in to stay on your own computer
- you only need it now and then, from one MCP client

## How much does the eDesk API cost?

Free 7-day trial with 2,000 credits, no card needed. After that, the eDesk API is pay as you go with no limit on apps: Credit packs from $29 for 5,000 credits, one-time, no subscription. A successful call uses 20 to 30 credits (25 for most tools, about $0.10 to $0.15), your Cloud Browser uses 50 credits a day while it has an app enabled for agents, however many apps that is, and an agent driving the browser itself uses 5 credits a minute. Credit packs stay valid for 12 months and stack, so unused credits carry over.

| Credits | Price, one time | Calls at 25 credits | Per 1,000 credits |
|---|---|---|---|
| 5,000 | $29 | 200 | $5.80 |
| 15,000 | $79 | 600 | $5.27 |
| 32,000 | $149 | 1,280 | $4.66 |
| 60,000 | $249 | 2,400 | $4.15 |

Only successful calls use credits; failed calls and timeouts cost nothing. At a balance of 0 calls pause, never a surprise charge. Authenticate with the `Authorization: Bearer` header. [See full pricing](https://cotlet.dev/pricing.md)

## How Cotlet holds your access

Cotlet hosts MCP servers and REST APIs for apps with no usable API. Your agent works in your own eDesk account.

- **Company details:** Cotlet is run by Take Group sp. z o.o., a company registered in Poland. Its full address and registration numbers are in the Terms of service. [Terms of service](https://cotlet.dev/terms)
- **Your sign-in:** You sign in to eDesk yourself, in your own Cloud Browser: a Chrome we run for you in the EU, one per app. We never save your password (password saving is off), the profile is stored encrypted with AES-256-GCM, and your agents get eDesk only after you enable it. When eDesk signs you out, your agent gives you a link to sign in again. [Security](https://cotlet.dev/security.md)
- **Revoking access:** Press Disable for agents next to eDesk, sign out of eDesk in your Cloud Browser, or reset the browser. Every background request is listed in your Background activity. Actions that reach other people wait for your OK unless you switch that off per tool.
- **What we never do:** Store passwords, solve CAPTCHAs or bypass MFA.
- **eDesk's terms:** You use your own eDesk account and stay responsible for following eDesk's terms. Cotlet is independent and not affiliated with eDesk. [Terms](https://cotlet.dev/terms)
- **Contact:** Questions about the company, security or an app: [contact@cotlet.dev](mailto:contact@cotlet.dev)

## Frequently asked questions

**How do I get access?**

Sign up free, open eDesk in the console and press Request access. Then you create your API key and connect eDesk there.

**Do I need to be technical?**

No. You sign in to eDesk once in your Cloud Browser, a normal Chrome you open from the console, and paste one command into your agent, or one URL into n8n. Your agent can walk you through it. There is no server to install, update or fix.

**Is it safe to connect eDesk to Cotlet?**

Yes. You sign in to eDesk yourself, in your own Cloud Browser in the EU, and we never save your password. Your agents only get eDesk once you enable it, every background request is listed, and the browser profile is stored encrypted with AES-256-GCM, the cipher 1Password uses for its vaults. The AI model never sees a login, posts and messages wait for your OK, and Disable for agents cuts access in one click. Independent scanners grade cotlet.dev A+ on Qualys SSL Labs, securityheaders.com and Mozilla Observatory; live results are on https://cotlet.dev/security.

**Is a hosted server safer than a local one? My eDesk sign-in would leave my computer.**

On Cotlet you sign in inside your own Cloud Browser, which only you open, and its profile is stored encrypted with AES-256-GCM in the EU. Agents get only the apps you enable, and every background request is listed. A local server keeps your eDesk cookie in a plain file on your computer, readable by any program you run, and stops when your computer is off.

**Why does Cotlet send requests instead of clicking in my browser?**

To be fast, Cotlet doesn't click through eDesk's pages. It sends the same requests your browser would, from your browser's IP with its cookies, without opening a window. eDesk sees the same browser and IP you signed in with, and every request is listed in your Background activity.

**What if someone gets my Cotlet API key?**

The key holds no eDesk login or cookies, it only asks Cotlet to run a tool. It can call only the apps and tools you gave it, and a read-only key changes nothing. Anything that reaches other people, like posts, comments or messages, waits for your OK in the dashboard by default, so a leaked key cannot post or message as you. When you switch approval off for a scheduled job, give that job its own key limited to that one tool. Every call is in your activity log, and deleting the key ends access at once.

**Why a signed-in browser and not OAuth, like other integration platforms?**

eDesk offers no OAuth token you can simply grant for these tools: its official API leaves them out or needs a developer app, a plan or an approval first (see the official API section above). That is why Cotlet sets the limits itself: per key, per tool, with your approval before anything reaches other people. Cotlet is run by Take Group sp. z o.o., an EU company (VAT PL6342984273).

**Do I need eDesk Enterprise to use this?**

No. eDesk's own API and API tokens need the Enterprise plan and an Admin login (eDesk Help: Getting started with the eDesk API). Cotlet works in your own eDesk login on your plan instead. Your role still counts: eDesk Help says replying and creating tickets need Basic mailbox access or higher, and Read-only users cannot.

**What can it not do?**

Nothing creates a ticket, merges tickets, sends a bulk reply, schedules a send or attaches files. Message Rules, templates and channels are read only or out of reach, and Cotlet changes no settings. A sent reply cannot be unsent, which is why each reply asks for your OK by default.

**Can my agent post or send messages in eDesk without asking me?**

No. Every call to reply_to_ticket, add_internal_note or update_ticket waits for your OK by default. For scheduled automations you can switch confirmation off per tool in your dashboard, for example only for approvals.

**Can I use the eDesk API in n8n?**

Yes. Add https://cotlet.dev/mcp/v1 with your API key in n8n's MCP Client node, or call its endpoints under https://cotlet.dev/api/v1/edesk from the HTTP Request node.

---

Give your AI agents your signed-in browser.

**Product:** [Integrations](https://cotlet.dev/integrations.md) · [Use cases](https://cotlet.dev/use-cases.md) · [How it works](https://cotlet.dev/how-it-works.md) · [Pricing](https://cotlet.dev/pricing.md) · [Security](https://cotlet.dev/security.md)

**Resources:** [Blog](https://cotlet.dev/blog.md) · [API docs](https://cotlet.dev/docs.md) · [Help center](https://cotlet.dev/help.md) · [Changelog](https://cotlet.dev/changelog.md) · [GitHub](https://github.com/cotletdev/cotlet)

**Solutions:** [For developers](https://cotlet.dev/for-developers.md) · [For automation agencies](https://cotlet.dev/for-agencies.md)

**Company:** [About](https://cotlet.dev/about.md) · [AI info: company facts](https://cotlet.dev/ai-info.md) · [Contact](https://cotlet.dev/contact.md)

**Legal:** [Terms of service](https://cotlet.dev/terms) · [Privacy policy](https://cotlet.dev/privacy) · [Refund policy](https://cotlet.dev/refunds) · [Acceptable use](https://cotlet.dev/acceptable-use) · [Cookie policy](https://cotlet.dev/cookies) · [DPA](https://cotlet.dev/dpa) · [Subprocessors](https://cotlet.dev/subprocessors)

**Elsewhere:** [Status page](https://status.cotlet.dev) · [Cotlet on GitHub](https://github.com/cotletdev) · [Cotlet on X](https://x.com/cotletdev) · [Cotlet on LinkedIn](https://www.linkedin.com/company/cotletdev) · [Cotlet on Product Hunt](https://www.producthunt.com/products/cotlet) · [Cotlet on Crunchbase](https://www.crunchbase.com/organization/cotlet) · [Cotlet on SaaSHub](https://www.saashub.com/cotlet)

Cotlet is an independent service. It is not affiliated with, endorsed by or sponsored by any of the products listed on this site. Product names are trademarks of their respective owners.

## For AI agents: sign your user up

Is your user asking you to sign them up for Cotlet? You can do it for them, no account or key needed.

1. Read the fields and their allowed values: GET https://cotlet.dev/api/v1/access-requests
2. Ask the user for each value: email, apps, what you will do with them. If they leave the password to you, generate a strong one and show it to them.
3. Show the user what you will send, then POST it as JSON to https://cotlet.dev/api/v1/access-requests.

One call creates the account and sends the access request; we email the user when access is granted.