SuprSend (BYOK)

SuprSend (BYOK) — connector documentation

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

What SuprSend (BYOK) is for

SuprSend (BYOK) lets an AI assistant read your own SuprSend data through the SuprSend API with a key you supply (SuprSend workspace API key). Read-only: 11 tools (list_users, get_user, list_messages, get_message_content, list_workflows, list_templates, list_events, list_tenants, list_subscriber_lists, get_subscriber_list, list_objects). 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 hub.suprsend.com. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by SuprSend. SuprSend 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 users exist in my SuprSend workspace?"
• "What properties are stored for user ada-42 in SuprSend?"
• "Did any SuprSend email messages fail yesterday?"
• "What did message abc123 actually say?"
• "Which workflows are live in my SuprSend production workspace?"
• "Which notification templates do I have and on which channels?"

What it does

• list_users: List users (recipients) in the workspace by creation order, with ID and created and updated times; cursor-paginated.
• get_user: Get one user by distinct ID: created and updated times and the custom properties stored on the profile.
• list_messages: List messages sent through the workspace, newest first, with channel, delivery status, timestamps and failure reason; filter by channel, workflow, recipient or date.
• get_message_content: Get the rendered content of one sent message (channel and content body).
• list_workflows: List notification workflows in a workspace with name, slug, status, category, trigger type and last execution time.
• list_templates: List notification templates in a workspace with name, slug, enabled channels, status and last triggered time.
• list_events: List the events that can trigger workflows, with name, description and creation time.
• list_tenants: List tenants (brands or customer accounts) with name, timezone, blocked channels and hierarchy level.
• list_subscriber_lists: List subscriber lists in the workspace (use get_subscriber_list for one list's configuration).
• get_subscriber_list: Get one subscriber list's configuration: name, type, subscriber count, source, status and sync settings.
• list_objects: List objects of one type (such as teams or organizations) that users can subscribe to, with subscription counts; cursor-paginated.

BYOK key

You bring your own SuprSend SuprSend workspace API key (https://docs.suprsend.com/reference/authentication). 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 hub.suprsend.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.

Notices

The API key belongs to one workspace (for example staging or production); pass the same workspace slug to the tools that ask for it.

Data sources

• https://docs.suprsend.com/reference/overview (the API this connector calls, with a BYOK key)

Live from the SuprSend API (hub.suprsend.com) with a BYOK key; documentation: https://docs.suprsend.com/reference/overview. 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 SuprSend. SuprSend 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 SuprSend account.

Built for: Worldwide. Languages: English.

SuprSend (BYOK) — Privacy Policy

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

What SuprSend (BYOK) is. SuprSend (BYOK) is a connector (an MCP server and REST API) that an AI assistant calls on your behalf to read your own SuprSend data: Read your SuprSend notification workspace: users, messages and delivery status across email, SMS and push, workflows, templates, events, tenants and lists with your own API key. You bring your own SuprSend SuprSend workspace API key; the assistant sends it to us with each request.

BYOK key. The key you supply is used to make the one SuprSend 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 hub.suprsend.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 SuprSend 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 SuprSend receives. The request we make on your behalf, including the key and the arguments, under SuprSend's own terms and privacy policy. SuprSend acts at your direction and is the only recipient of the data of your request besides our hosting provider.

What we return. The answer SuprSend 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 SuprSend 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. SuprSend (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 SuprSend at any time to end all access.

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

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

SuprSend (BYOK) — Terms of Service

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

1. The Service. SuprSend (BYOK) provides: Read your SuprSend notification workspace: users, messages and delivery status across email, SMS and push, workflows, templates, events, tenants and lists with your own API key. 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 SuprSend credentials and only access data you are allowed to access. SuprSend's terms apply to your use of SuprSend; 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 SuprSend. SuprSend 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 SuprSend returns, lightly trimmed; it may be incomplete, delayed or changed by SuprSend. Check important facts at the source.
5. Read-only. The Service does not create, change, send or delete anything in your SuprSend 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 SuprSend'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; SuprSend 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 SuprSend 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 SuprSend 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-suprsend

SuprSend (BYOK) support

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

• MCP endpoint: https://byok-suprsend.connectorbay.com/mcp
• REST API: https://byok-suprsend.connectorbay.com/openapi.json
• Live status: https://byok-suprsend.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. SuprSend (BYOK) never asks for them.