Integrations / Brevo

Brevo

Brevo transactional email (SMTP API) — send emails, inspect templates, review delivery statistics/events, manage transactional-contact and domain blocklists, and read inbound-parsing events.

OAuth 2.0

Indexes

Actions

What Telara does

Capability matrix

Indexes Yes Tracks spend No Discovers shadow AI No Runs actions Yes Real-time events No

Before you connect

Prerequisites

A Brevo (formerly Sendinblue) account you can administer.

Account owner or a user who can open SMTP & API.

Vendor setup

Get the credential

Open API Keys

In Brevo, go to the account menu → SMTP & API → API Keys.

Create a v3 key

Click Generate a new API key. Name it for Telara. Copy it immediately. Brevo sends this as an api-key header, not a Bearer token — Telara’s form handles that.

Paste in Telara

Settings → Integrations → Brevo. Paste the key into the field Telara shows.

Permissions Telara requests

transactional.email:read
OAuth 2.0
transactional.email:write
OAuth 2.0

In Telara

Connect in Telara

OAuth 2.0

Brevo OAuth 2.0 authorization-code connection for transactional-email reads and writes, including SMTP templates, events, reports, and blocklists. Register only these scopes in the Brevo app; the access token is sent as Authorization Bearer.

In Telara, open Settings → Integrations, choose this connector, and click Connect. Telara sends you to the vendor to approve access, then returns you here. You do not create an OAuth app or paste a client secret.

API key

Brevo API key (v3), sent as a raw value in the `api-key` request header — confirmed against the reference spec's securitySchemes (apiKey scheme, in: header, name: api-key; not a Bearer token, no prefix). Create one under Brevo Account > SMTP & API > API Keys.

In Telara, open Settings → Integrations, choose this connector, and paste the key into the fields Telara shows.

Fields Telara asks for

API key

Knowledge

What gets indexed

Resource	Coverage
Template	Partial — not every record the vendor holds is synced

Sync

Freshness & sync

Resource	Lag	Deletions
Template	Up to 1 day	Removed records disappear on the next full sync

Data handling

Permissions & data handling

The scopes above are the permissions this connector requests. They come from the catalog, not from a hand-written page.

Excluded from semantic search: Template.

After connect

Verify it worked

After you save, Telara runs a read-only check against the account. The integration shows as connected when that check succeeds.

Honesty

Known limitations

SMTP keys and v3 API keys are different. Use the API Keys tab, not the SMTP login.

A key created on a sub-account only sees that sub-account.