Brevo
Collect account info and verified-sender inventory as read-only 'who can send as us' access-review evidence through the Brevo (Sendinblue) API. Scoped strictly to access evidence, not campaign or contact data. Brevo's confirmed team/user-management endpoints are gated behind its Corporate/multi-account plan tier and are not confidently documented for standard accounts, so 'who has admin' evidence is NOT covered here -- track it manually until confirmed.
What this connector audits
Checks this connector runs once it's connected. This is the full list; we don't claim coverage beyond what's implemented.
- Account plan/company info (read-only)
- Verified sender inventory
- Team-member/admin-role evidence NOT covered for standard accounts (no confirmed endpoint) -- track manually
Endpoints this template queries
The exact Brevo API endpoints called once connected. All read-only GET requests unless noted.
- GET/account
- GET/senders
What we need
Field labels only. We never show secret values here. Credentials are encrypted at rest and used only to run the checks above.
- Base URL(prefilled: https://api.brevo.com/v3)
- Endpoints (JSON)(prefilled: [ { "id": "account", "name": "Account", "path": "/account" }, { "id": "senders", "name": "Verified senders", "path": "/senders" } ])
- Auth header name(prefilled: api-key)
- Auth header value(secret credential)
Required
Optional
Which frameworks this evidence supports
Brevo evidence feeds into controls for any framework you run that requires this check type; the same synced evidence can satisfy more than one framework's requirements instead of being collected per audit.
Don't see your system?
Tell us what you use and what it needs to prove. We'll follow up about adding a connector.
Wire in Brevo evidence
Get a guided demo, or start by scanning any domain for free.