[Cotlet](https://cotlet.dev/index.md) · [All integrations](https://cotlet.dev/integrations.md) · [MCP servers](https://cotlet.dev/integrations/mcp.md) · [APIs](https://cotlet.dev/integrations/api.md) · [API & MCP status](https://cotlet.dev/api-status.md) · [How it works](https://cotlet.dev/how-it-works.md) · [Security](https://cotlet.dev/security.md) · [Custom API](https://cotlet.dev/custom-api.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)

# Mailshake API status Does Mailshake have an API or MCP server?

> Mailshake has a public API with keys a team creates, push webhooks and apps on Zapier and Make; no MCP server found (checked 20 Nov 2026). Cotlet API & MCP access score: 4 out of 5. What exists instead, with sources.

Source: https://cotlet.dev/api-status/mailshake

Mailshake has a public API as of 20 November 2026: "To get your API key, go to the Extensions > API page in Mailshake and create your key." It reads and writes campaigns, recipients and leads, and with its push subscriptions Mailshake sends a request to your own URL for events such as clicks. Mailshake has apps on Zapier and Make with actions such as Add Recipient, and campaign results export to CSV. No Mailshake MCP server was found.

**Cotlet API & MCP access score: 4 out of 5.** A Mailshake team can add prospects from Zapier or Make, and a developer can build on the API and its push events. No official way for ChatGPT or Claude to read or answer replies in Lead Catcher was found.

Checked 20 Nov 2026 ·[How Cotlet scores](#how-cotlet-scores)·[Report an inaccuracy](mailto:contact@cotlet.dev?subject=Mailshake%20API%20status)

Cotlet publishes this page as an independent assessment. Cotlet is not affiliated with, endorsed by or sponsored by Mailshake. Mailshake is a trademark of its owner. If Mailshake's own tools cover what you need, use them first.

Mailshake API & MCP report

4/5

Cotlet API & MCP access score 7/10 points

Public API

3/3

MCP server

0/3

Zapier · Make · n8n

2/2

Webhooks

1/1

Data export

1/1

Checked

20 Nov 2026

[Report an inaccuracy](mailto:contact@cotlet.dev?subject=Mailshake%20API%20status) [How we score](#how-cotlet-scores)

Public API

Yes

3 of 3

MCP server

None

0 of 3

Zapier · Make · n8n

Zapier, Make

2 of 2

Webhooks

Push API

1 of 1

Data export

CSV

1 of 1

On this page

1. [01 At a glance](#at-a-glance)
2. [02 API](#public-api)
3. [03 Zapier, Make, n8n](#automation)
4. [04 Webhooks](#webhooks)
5. [05 MCP server](#mcp-server)
6. [06 Data export](#export)
7. [07 Routes](#routes)
8. [08 How Cotlet scores](#how-cotlet-scores)
9. [09 Sources](#sources)

01 · At a glance

## Mailshake API & MCP access at a glance

__Mailshake API & MCP access on 20 Nov 2026 7 of 10 points__
| Check | Points | Finding | Source |
| ------------------------- | ------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------ |
| Public API for businesses | 3 / 3 | Yes: a team creates its own API key under Extensions, API, and reads and writes campaigns, recipients and leads | [\[1\]](#source-1) |
| Official MCP server | 0 / 3 | No Mailshake MCP server, ChatGPT app or Claude app found on mailshake.com, docs.mailshake.com or the MCP Registry | [\[4\]](#source-4) |
| Zapier, Make, n8n | 2 / 2 | Zapier: triggers such as New Open and New Click and actions such as Add Recipient. Make: a verified app with actions such as adding recipients to a campaign and pausing a campaign. No app found on n8n | [\[2\]](#source-2)[\[3\]](#source-3) |
| Webhooks | 1 / 1 | Yes: with push subscriptions you create with your API key, Mailshake sends a request to your own URL for events such as a click | [\[1\]](#source-1) |
| Data export | 1 / 1 | Campaign prospects, sent messages and list-cleaning results export to CSV | [\[5\]](#source-5) |

One more fact that earns no points: Mailshake's API docs say "each application has its own quota limits based on your Mailshake subscription", and name no plan that API keys need (checked 20 November 2026) ([Mailshake API docs](https://api-docs.mailshake.com/)).

02 · API

## Does Mailshake have an API?

Yes

Mailshake has a public API. Its API docs say: "To get your API key, go to the Extensions > API page in Mailshake and create your key." With the key, a team reads and writes its campaigns, recipients and leads.

[ Source \[1\] · Mailshake API documentation ](#source-1)

03 · Zapier, Make, n8n

## Does Mailshake work with Zapier, Make or n8n?

Zapier and Make

Mailshake has a Zapier app with triggers such as New Click, New Open and New Lead Status, and an Add Recipient action that "Adds a single recipient to a campaign." Its verified Make app has actions such as Add Recipients to the Campaign and Pause/Unpause Campaign. No Mailshake app was found on n8n, where the page returned 404 (checked 20 November 2026).

[ Source \[2\] · Zapier: Mailshake integrations ](#source-2)

04 · Webhooks

## Does Mailshake have webhooks?

Yes, push API

Mailshake's API has push subscriptions: a call that "Starts a subscription for a type of push", for events such as Clicked, Opened, Replied and LeadCreated. Mailshake's docs say: "Mailshake will make a HTTP request to your servers so you can react in real time." A team sets them up with its own API key.

[ Source \[1\] · Mailshake API documentation ](#source-1)

05 · MCP server

## Does Mailshake have an MCP server?

None found

Mailshake: no MCP server, ChatGPT app or Claude app found on mailshake.com, docs.mailshake.com or in the official MCP Registry on 20 November 2026.

[ Source \[4\] · Official MCP Registry, search for "mailshake", 20 Nov 2026: no server from Mailshake ](#source-4)

06 · Data export

## Can I export my Mailshake data?

CSV

Mailshake's help center describes exporting campaign prospects, sent messages and list-cleaning results from Campaigns: "Once the export is done processing, click Download CSV".

[ Source \[5\] · Mailshake Help: How do I export my campaign results? ](#source-5)

07 · Routes

## How can I connect Mailshake to ChatGPT or Claude today?

A Mailshake business has three routes today, and they do different jobs.

app.mailshake.com Your Mailshake business account

1. Route 1  
### The Mailshake API and push events  
A key your team creates, for code you write.

  - Answer replies: with code
  - Add prospects to campaigns: with code
  - Results elsewhere: with code
2. Route 2  
### Zapier and Make  
Triggers for opens, clicks and lead statuses, and actions that add recipients.

  - Answer replies: no
  - Add prospects to campaigns: Add Recipient
  - Results elsewhere: events only
3. Route 3  
### [A cloud browser](https://cotlet.dev/integrations/mailshake-api-mcp-server.md)  
You sign in to your Mailshake business account in a browser that runs in the cloud, and your AI agent works on the screens you use: campaigns, prospects, Lead Catcher, Sending Calendar. Cotlet, which publishes this page, is a cloud browser of this kind.

  - Answer replies: with your login
  - Add prospects to campaigns: with your login
  - Results elsewhere: with your login

To connect your AI: [Mailshake MCP server](https://cotlet.dev/integrations/mailshake-api-mcp-server.md).

08 · How Cotlet scores

## How Cotlet scores API & MCP access

Cotlet scores one thing: how easily a business can connect its own software or AI agent to its own account. Five checks give up to 10 points, and the points give the Cotlet API & MCP access score, from 1 to 5.

Points to score

Mailshake · 7 points
1. 1 0 or 1
2. 2 2 to 4
3. 3 5 or 6
4. 4 7 or 8
5. 5 9 or 10

Where the 10 points come from

1. API 3 of 3
2. MCP 0 of 3
3. Zapier, Make, n8n 2 of 2
4. Webhooks 1 of 1
5. Data export 1 of 1

__How Cotlet scores API & MCP access: the five checks__
| Check | Points | What earns them |
| ------------------------------------- | ------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Official API for the business account | 0 to 3 | 3: public and self-serve, reads and writes. 2: public, but read only or on a higher plan. 1: by partner approval or as a paid add-on. 0: none |
| Official MCP server | 0 to 3 | 3: reads and writes the business account. 2: works on the business account, read only or limited. 1: exists, but not for the business account, such as an app in ChatGPT for clients. 0: none |
| Zapier, Make, n8n | 0 to 2 | 2: an app on two or more of them, with actions. 1: an app on one, or triggers only. 0: none |
| Webhooks | 0 or 1 | 1: documented webhooks for business events |
| Data export | 0 or 1 | 1: an official export, such as CSV, a report download or a data add-on |

__How Cotlet scores API & MCP access: points to score__
| Points | Score |
| ------- | ---------- |
| 9 or 10 | 5 out of 5 |
| 7 or 8 | 4 out of 5 |
| 5 or 6 | 3 out of 5 |
| 2 to 4 | 2 out of 5 |
| 0 or 1 | 1 out of 5 |

Every score rests on the sources listed on the page and carries the date it was checked. A score changes when the facts change. Cotlet sells a cloud browser that connects AI agents to web apps such as Mailshake, and says so on every page of this catalog.

09 · Sources

## Sources

1. \[1\]  
[Mailshake API documentation](https://api-docs.mailshake.com/)  
api-docs.mailshake.com Checked 20 Nov 2026
2. \[2\]  
[Zapier: Mailshake integrations](https://zapier.com/apps/mailshake/integrations)  
zapier.com Checked 20 Nov 2026
3. \[3\]  
[Make: Mailshake, a verified app maintained by Make; n8n.io/integrations/mailshake returns 404, 20 Nov 2026](https://www.make.com/en/integrations/mailshake)  
make.com Checked 20 Nov 2026
4. \[4\]  
[Official MCP Registry, search for "mailshake", 20 Nov 2026: no server from Mailshake](https://registry.modelcontextprotocol.io/v0/servers?search=mailshake)  
registry.modelcontextprotocol.io Checked 20 Nov 2026
5. \[5\]  
[Mailshake Help: How do I export my campaign results?](https://docs.mailshake.com/article/119-how-do-i-export-my-campaign-results)  
docs.mailshake.com Checked 20 Nov 2026
6. \[6\]  
[Mailshake Terms of Service, last revised 11 Dec 2022](https://mailshake.com/terms/)  
mailshake.com Checked 20 Nov 2026

## Something changed at Mailshake?

Write to contact@cotlet.dev and we recheck this page.

[Report an inaccuracy](mailto:contact@cotlet.dev?subject=Mailshake%20API%20status) [Connect Mailshake to your AI](https://cotlet.dev/integrations/mailshake-api-mcp-server.md)

---

Give your AI agents your signed-in browser.

**Product:** [Integrations](https://cotlet.dev/integrations.md) · [MCP servers](https://cotlet.dev/integrations/mcp.md) · [APIs](https://cotlet.dev/integrations/api.md) · [API & MCP status](https://cotlet.dev/api-status.md) · [How it works](https://cotlet.dev/how-it-works.md) · [Pricing](https://cotlet.dev/pricing.md) · [Security](https://cotlet.dev/security.md) · [Custom API](https://cotlet.dev/custom-api.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.dev is built by Bart Krawczyk and Jake Slugocki, the founders of Take Group sp. z o.o., ul. Wincentego Janasa 4, 40-855 Katowice, Poland. KRS 0000871398, NIP 6342984273, VAT EU: PL6342984273. [About us](https://cotlet.dev/about.md)

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.
