Skip to navigation
Getting started

Authentication schemes

Choose between API key and OAuth 2.0 authentication for the Brevo API
View as Markdown
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 authorize your app, or connect your own backend as a machine-to-machine (M2M) client.

When to use?
Building an app that acts on behalf of a user, or a backend integration calling the API as itself.

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, or when your backend needs a scoped, short-lived credential instead of a static API key. Create and manage OAuth apps with the Brevo CLI: private apps work instantly, and public apps, which any Brevo account can authorize, go through a review by Brevo first.

Best for:

  • Apps acting on behalf of a user
  • Server-to-server integrations, via machine-to-machine (M2M)
  • Private integrations within an organisation
  • Public integrations that any Brevo account can connect, after review (Private and public apps)

See OAuth 2.0 to get started.