Zenvia (BYOK) — connector documentation
- MCP endpoint:
https://byok-zenvia.connectorbay.com/mcp - REST API:
POST https://byok-zenvia.connectorbay.com/v1/tools/{tool_name}, described by the OpenAPI 3.1 spec athttps://byok-zenvia.connectorbay.com/openapi.json - Transport: Streamable HTTP, stateless, MCP specification 2025-06-18 or later
- Authentication: your own Zenvia Zenvia API token, sent in the
X-Upstream-Keyheader of every request (never stored, logged or cached) - Health:
https://byok-zenvia.connectorbay.com/health· Tool schemas:https://byok-zenvia.connectorbay.com/tools.json - Publisher: Unify Dynamics LLC · connectorbay.com/byok-zenvia · agent@connectorbay.com
What Zenvia (BYOK) is for
Zenvia (BYOK) lets an AI assistant read your own Zenvia data through the Zenvia API with a key you supply (Zenvia API token). Read-only: 9 tools (list_templates, get_template, list_webhook_subscriptions, list_tickets, list_ticket_status_changes, list_contact_lists, list_contact_batches, list_contact_custom_fields, get_platform_status). 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.zenvia.com. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Zenvia. Zenvia 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 of my Zenvia WhatsApp templates are approved?"
- "Show the text and review status of Zenvia template 7a3f0c12-aaaa-4bbb-8ccc-0123456789ab"
- "Which webhooks are active on my Zenvia account?"
- "Which Zenvia support tickets are still open?"
- "How did Zenvia ticket T-1001 move through statuses?"
- "How many contacts are in each of my Zenvia lists?"
What it does
list_templates: List message templates (WhatsApp, SMS, RCS, e-mail, Facebook) with channel, category, approval status and quality score.get_template: Get one message template by id with its body text, header, status and review comments.list_webhook_subscriptions: List webhook subscriptions (event type, status, version, target URL) that receive Zenvia events; request headers and credentials are left out.list_tickets: List support tickets with subject, status, urgency, category, owner team and response and solution times.list_ticket_status_changes: List the status changes of one support ticket in order, to see how it progressed.list_contact_lists: List contact lists (static audiences) with name, size and dates; contacts themselves are not returned.list_contact_batches: List contact import batches with file name, status, line count and processed or failed record counts.list_contact_custom_fields: List the custom contact data fields defined on the account with their type.get_platform_status: Show the live status of Zenvia platform groups and components (UP, WARNING, DOWN).
BYOK key
You bring your own Zenvia Zenvia API token (https://app.zenvia.com/home/api). 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.zenvia.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://zenvia.github.io/zenvia-openapi-spec/v2/ (the API this connector calls, with a BYOK key)
Live from the Zenvia API (api.zenvia.com) with a BYOK key; documentation: https://zenvia.github.io/zenvia-openapi-spec/v2/. 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 Zenvia. Zenvia 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 Zenvia account.
Built for: Worldwide. Languages: English.