Authentication schemes
Choose between API key and OAuth 2.0 authentication for the Brevo API
API Key
Use a secret token for direct API access.
When to use?
Direct integrations and server-to-server communication where you control both endpoints.
OAuth 2.0
Let users in your organisation authorize your app to act on their behalf.
When to use?
Private integrations within your organisation — set up in minutes with the Brevo CLI.
API key authentication
Use API key authentication for direct API access. Include your API key in the api-key header for each request.
Best for:
- Direct API integrations
- Server-to-server communication
- Testing and development
See API Key authentication for setup instructions.
OAuth 2.0 authentication
Use OAuth 2.0 when your application needs to act on behalf of a Brevo user. Create and manage OAuth apps instantly with the Brevo CLI — no form, no manual approval.
Best for:
- Apps acting on behalf of a user
- Private integrations within an organisation
- Delegated access with user consent
See OAuth 2.0 to get started.
