Brevo-compatible API

Every Inklura site exposes, at https://<site-domain>/api/brevo/v3, a wire-compatible implementation of the Brevo v3 (ex-Sendinblue) REST API: same paths, same api-key header, same JSON bodies, integer ids, same error codes and bodies ({ "code", "message" }).

Code, SDKs and plugins written for Brevo work by changing only the base URL and the key. Email leaves through the site's own infrastructure (the site's sending configuration, send log, open and click tracking, bounce processing), not through Brevo.

curl https://<site-domain>/api/brevo/v3/account \
  -H "api-key: xkeysib-…" \
  -H "accept: application/json"

With no key, or an unknown or revoked key, the API answers 401 with { "code": "unauthorized", "message": "Key not found" }.

Tip

Try every operation in the interactive explorer: enter your site's domain and your key, send the request, copy the cURL, Node, PHP or Python sample.

What is covered

All 74 operations of these sections of the Brevo v3 specification:

Brevo section Content
Transactional emails sending (templates, params, versions, attachments, scheduling), logs, events, reports, templates, blocklist
Contacts contacts, lists, folders, attributes, import, export, double opt-in
Senders / Domains senders, sending domains and DNS verification
Webhooks subscriptions and real delivery of transactional events
Account / Process account, asynchronous processes (import, export)

Campaigns, SMS, WhatsApp, CRM, e-commerce and conversations are not available yet (see Compatibility).

How it works

  • One account = one site. An API key belongs to one tenant and one site; all data (contacts, lists, templates, logs) is isolated per site. Keys have the same format as Brevo keys (xkeysib-…), so plugins' key format checks pass.
  • Sending. POST /smtp/email goes through the same pipeline as the site's other email: sender and relay configured in the console, send log, tracking pixel.
  • Events. Every step (request, delivery, open, click, bounce, block) feeds /smtp/statistics/* and triggers your webhooks in Brevo's format.
  • Security. Keys are stored hashed, data is strictly isolated per site, and no caller-supplied URL (import, attachments, webhooks) can target an internal address.

Pages