Mailshake (BYOK)

Mailshake (BYOK) — connector documentation

• MCP endpoint: https://byok-mailshake.connectorbay.com/mcp
• REST API: POST https://byok-mailshake.connectorbay.com/v1/tools/{tool_name}, described by the OpenAPI 3.1 spec at https://byok-mailshake.connectorbay.com/openapi.json
• Transport: Streamable HTTP, stateless, MCP specification 2025-06-18 or later
• Authentication: your own Mailshake Mailshake API key, sent in the X-Upstream-Key header of every request (never stored, logged or cached)
• Health: https://byok-mailshake.connectorbay.com/health · Tool schemas: https://byok-mailshake.connectorbay.com/tools.json
• Publisher: Unify Dynamics LLC · connectorbay.com/byok-mailshake · agent@connectorbay.com

What Mailshake (BYOK) is for

Mailshake (BYOK) lets an AI assistant read your own Mailshake data through the Mailshake API with a key you supply (Mailshake API key). Read-only: 11 tools (get_me, list_campaigns, get_campaign, list_recipients, get_recipient, list_leads, get_lead, list_replies, list_sent_messages, list_senders, list_team_members). The BYOK key travels with each request, is used for that one call only and is never stored, logged or cached; it is only ever sent to api.mailshake.com. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Mailshake. Mailshake and its logos are trademarks of their owners and are used only to say which service the connector works with.

Ask your assistant things like:

• "Which Mailshake user is my API key for?"
• "What Mailshake campaigns do I have?"
• "Show Mailshake campaign 1"
• "Who is in Mailshake campaign 1?"
• "Show Mailshake recipient john@doe.com in campaign 1"
• "Which Mailshake leads are open?"

What it does

• get_me: Show the Mailshake user the key belongs to: name, email, team name and whether the user is a team admin.
• list_campaigns: List Mailshake campaigns with title, creation date and paused or archived flags. 10 quota units per call.
• get_campaign: Get one Mailshake campaign with its message sequence (initial, follow-up, drip), sender and link.
• list_recipients: List the recipients of a Mailshake campaign with name, email and paused flag. Filter by search text.
• get_recipient: Get one Mailshake recipient by recipient id, or by campaign id plus email address.
• list_leads: List Mailshake leads (recipients worth following up) with status, campaign and assignee. Filter by status, campaign, assignee or text.
• get_lead: Get one Mailshake lead by lead id, recipient id, or campaign id plus email address.
• list_replies: List the most recent replies to your Mailshake emails (also bounces, out-of-office and unsubscribe notices) with recipient, campaign, subject and plain-text body. Up to 25 per call.
• list_sent_messages: List the most recently sent Mailshake emails with recipient, campaign, subject and send time (bodies are left out). Up to 25 per call.
• list_senders: List the connected sender email addresses of your Mailshake team.
• list_team_members: List the users of your Mailshake team with name, email and admin flag.

BYOK key

You bring your own Mailshake Mailshake API key (https://api-docs.mailshake.com/#getting-your-api-key). Your assistant sends it in the X-Upstream-Key header with each request. ConnectorBay uses it for that one call only: it is never stored, logged or cached, never shown in an answer, and it is only sent to api.mailshake.com over https, with no redirects followed. Create a key with the fewest permissions the tools need (read-only if the provider offers it), and revoke it at the provider whenever you like.

Data sources

• https://api-docs.mailshake.com/ (the API this connector calls, with a BYOK key)

Live from the Mailshake API (api.mailshake.com) with a BYOK key; documentation: https://api-docs.mailshake.com/. Endpoints checked against that documentation on 2026-10-16.

What it is not

Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Mailshake. Mailshake and its logos are trademarks of their owners and are used only to say which service the connector works with. It is read-only: it never creates, changes, sends or deletes anything in your Mailshake account.

Built for: Worldwide. Languages: English.

Mailshake (BYOK) — Privacy Policy

Effective 24 October 2026. Unify Dynamics LLC ("we", "us"), Menlo Park, California.

What Mailshake (BYOK) is. Mailshake (BYOK) is a connector (an MCP server and REST API) that an AI assistant calls on your behalf to read your own Mailshake data: Read your Mailshake cold email campaigns, recipients, leads, replies, senders and team members with BYOK. You bring your own Mailshake Mailshake API key; the assistant sends it to us with each request.

BYOK key. The key you supply is used to make the one Mailshake call you asked for. Our application does not store it, write it to a log, put it in a cache, or share it. It is sent only to api.mailshake.com, over https, and is removed from any text we return to you or your assistant. We do not follow redirects with your key. If Mailshake rejects it, we say so without repeating it.

What we receive. The arguments of each tool call, the BYOK key (for that call only), the technical headers needed to serve the request (an IP address or a client identifier supplied by the assistant) and standard server logs. What Mailshake receives. The request we make on your behalf, including the key and the arguments, under Mailshake's own terms and privacy policy. Mailshake acts at your direction and is the only recipient of the data of your request besides our hosting provider.

What we return. The answer Mailshake gives for your request, trimmed to the fields the tool documents. We do not keep it: it is returned to your assistant and not stored, cached or used to train anything.

What we do not do. We do not build a profile, sell or share personal information, or keep your Mailshake data. Rate-limit counters (a client identifier and timestamps) are held in memory for at most 24 hours. Hosting access logs (IP addresses, request paths and status codes) are kept for up to 30 days for security and abuse prevention; our application adds no request headers or bodies to them.

Sub-processors. Mailshake (the API you call with a BYOK key, at your direction). Hosting: Vercel (United States regions).

Your rights. Because we store no personal data beyond short-lived logs, requests to access, correct or delete data are usually satisfied automatically; you can still contact agent@connectorbay.com and we will respond within 30 days. Revoke your key at Mailshake at any time to end all access.

Children. Mailshake (BYOK) is a general-audience service operated by the adult using the assistant, under Mailshake's own age rules.

Changes. We will post changes here with a new effective date.

Mailshake (BYOK) — Terms of Service

Effective 24 October 2026. These terms govern use of the Mailshake (BYOK) connector ("the Service") operated by Unify Dynamics LLC ("we", "us").

1. The Service. Mailshake (BYOK) provides: Read your Mailshake cold email campaigns, recipients, leads, replies, senders and team members with BYOK. It is accessed through an AI assistant or directly over MCP or HTTP, and is read-only.
2. Your own key, your own account. You must use your own Mailshake credentials and only access data you are allowed to access. Mailshake's terms apply to your use of Mailshake; you are responsible for complying with them, including any rate limits and permitted uses. Do not share a key you do not own.
3. Independent. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Mailshake. Mailshake and its logos are trademarks of their owners and are used only to say which service the connector works with.
4. No advice, no guarantees. Output is the data Mailshake returns, lightly trimmed; it may be incomplete, delayed or changed by Mailshake. Check important facts at the source.
5. Read-only. The Service does not create, change, send or delete anything in your Mailshake account.
6. Acceptable use. Automated use within the published rate limits is welcome. Do not use the Service to access data you are not entitled to, to circumvent Mailshake's controls, or to attack any system.
7. Availability. The Service is provided "as is" without warranty. We may change, limit or discontinue it at any time; Mailshake may change or end its API at any time.
8. Data. Our Privacy Policy describes what we process. In short: the BYOK key is used for the one call and not stored or logged.
9. Pro keys. Optional ConnectorBay Pro API keys are issued at our discretion and are separate from your Mailshake key.
10. Liability. To the fullest extent permitted by law, Unify Dynamics LLC is not liable for any loss arising from use of or reliance on the Service, including any action Mailshake takes on your account. Our total liability is limited to US $100.
11. Governing law. California law; venue in San Mateo County, California.
12. Contact. Unify Dynamics LLC · agent@connectorbay.com · https://connectorbay.com/byok-mailshake

Mailshake (BYOK) support

Email agent@connectorbay.com. We answer within two business days.

• MCP endpoint: https://byok-mailshake.connectorbay.com/mcp
• REST API: https://byok-mailshake.connectorbay.com/openapi.json
• Live status: https://byok-mailshake.connectorbay.com/health

When you report a problem, include the question you asked your agent, roughly when, and which agent you used (for example Claude, ChatGPT or Gemini). Never send us passwords, account numbers or ID numbers. Mailshake (BYOK) never asks for them.