Be the first to get access to new connectors. Get early access →
ConnectorBay Early access

Brevo SMS and WhatsApp (BYOK) — connector documentation

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

What Brevo SMS and WhatsApp (BYOK) is for

Brevo SMS and WhatsApp (BYOK) lets an AI assistant read your own Brevo SMS and WhatsApp data through the Brevo SMS and WhatsApp API with a key you supply (API key). Read-only: 9 tools (list_sms_campaigns, get_sms_campaign, list_sms_templates, list_whatsapp_campaigns, get_whatsapp_campaign, list_whatsapp_templates, get_whatsapp_account_status, get_transactional_sms_summary, list_transactional_sms_daily). 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.brevo.com. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Brevo SMS and WhatsApp. Brevo SMS and WhatsApp 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:

  • "How did my last Brevo SMS campaigns perform?"
  • "Show Brevo SMS campaign 11 with its delivery statistics"
  • "Which SMS templates are in my Brevo account?"
  • "How did my Brevo WhatsApp campaigns perform?"
  • "Show Brevo WhatsApp campaign 21"
  • "Which WhatsApp templates are approved in Brevo?"

What it does

  • list_sms_campaigns: List SMS campaigns with name, status, sender, schedule and sent dates and delivery statistics (sent, delivered, bounces, answers, unsubscriptions). Message text is not returned.
  • get_sms_campaign: Get one SMS campaign with status, sender, dates, statistics, tags and the names of its recipient and exclusion lists. Message text is not returned.
  • list_sms_templates: List SMS templates with id, name, creation and update dates, short-URL and Unicode flags. Template text is not returned.
  • list_whatsapp_campaigns: List WhatsApp campaigns with name, status, schedule, template id, read percentage and delivery statistics.
  • get_whatsapp_campaign: Get one WhatsApp campaign: status, dates, sender number, recipient list and segment ids, statistics and template name, category and language.
  • list_whatsapp_templates: List WhatsApp message templates with name, language, category, type, approval status and rejection reason, if any.
  • get_whatsapp_account_status: Show the WhatsApp Business setup: business status, phone number quality and name status, sending limit and account status.
  • get_transactional_sms_summary: Get aggregated transactional SMS counts (requests, delivered, bounces, blocked, replies, unsubscribes) for a date range or the last days.
  • list_transactional_sms_daily: Get day-by-day transactional SMS counts (requests, delivered, bounces, blocked, replies, unsubscribes) for a date range or the last days.

BYOK key

You bring your own Brevo SMS and WhatsApp API key (https://developers.brevo.com/docs/getting-started). 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.brevo.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

Live from the Brevo SMS and WhatsApp API (api.brevo.com) with a BYOK key; documentation: https://developers.brevo.com/reference/getsmscampaigns-1. 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 Brevo SMS and WhatsApp. Brevo SMS and WhatsApp 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 Brevo SMS and WhatsApp account.

Built for: Worldwide. Languages: English.