Brevo (formerly Sendinblue): 3 reads and 3 writes, one client
Transactional email, SMS and contacts. 300 emails a day on the free plan. Every call below is available over HTTP, through the SDK and as a tool for a coding agent, with the same arguments and the same meter.
What Brevo (formerly Sendinblue) can do here
The integration exposes 3 reads and 3 writes, each with a declared input and output schema rather than a page of documentation you would have to translate. Transactional email, SMS and contacts. 300 emails a day on the free plan.
How it authenticates
Brevo (formerly Sendinblue) authenticates with a apiKey, supplied per request or stored once against your account and sealed at rest. On our side the same value is read from apiKey when we broker the call for you.
Capabilities it fulfils
Brevo (formerly Sendinblue) answers email.send in the vendor-neutral form, which means code asking for that capability can be pointed at Brevo (formerly Sendinblue) without naming it. If it goes down, or you would rather use somebody else, that is a preference change and not a rewrite.
- getAccount — read: Plan, credits and account details. The cheapest call, so it is the connection test.
- sendEmail — write: Send one transactional email. REACHES A REAL PERSON — there is no undo.
- listContacts — read: Contacts in the account.
- createContact — write: Add a contact, optionally to lists.
- listTemplates — read: Stored transactional email templates.
- sendSms — write: Send one SMS. REACHES A REAL PHONE and consumes paid SMS credits — these are separate from the free email allowance.
Questions
Do I have to bring my own API keys?
You can, and that lane is free for ever — pass your key on the request or store it against your account, and we are one proxy hop. The paid lane is the other direction: we call 226 providers with our credentials so you never register anywhere. Both go through the same client and the same operation names.
What happens to a key I store here?
It is sealed with AES-256-GCM before it reaches the database and is only ever opened to make the call you asked for. It is scoped to your account, it is never logged, and deleting the connection deletes it. For an OAuth provider we hold a refresh token instead, and revoking the link at the provider stops the calls here immediately.
What happens when a provider changes its API?
The operation contract is declared, so a response that no longer matches is a refusal rather than a silently wrong answer. The contract does not coerce types — a field declared a number that arrives as a string is rejected at the edge, on the way in and on the way out.