For AI agents: a documentation index is available at the root level at /llms.txt and /llms-full.txt. Append /llms.txt to any URL for a page-level index, or .md for the markdown version of any page.
Help CenterAPI KeysStatusSign In
GuidesAPI ReferenceChangelog
GuidesAPI ReferenceChangelog
  • Getting started
    • Overview
    • Quickstart
    • Authentication
      • API key authentication
      • IP security
    • Rate limits
  • Messaging API
    • Send transactional email
    • Send transactional SMS
    • Send transactional WhatsApp
  • Marketing Platform
    • Manage your contacts
    • Track website activity
    • Send WhatsApp campaigns
    • Weekly event exports
  • Webhooks
    • Getting started
    • Conversations webhooks
    • Payment webhooks
    • Marketing webhooks
    • Transactional webhooks
    • Loyalty webhooks
    • Batched webhooks
    • Secure webhook calls
    • Meetings and phone webhooks
    • Push notification webhooks
    • Sales CRM webhooks
  • Conversations
    • Getting started
    • Customize the chat widget
    • JavaScript API reference
    • REST API reference
    • Conversations webhooks
  • eCommerce
    • Activate eCommerce app
    • Manage product categories
    • Manage products
    • Manage orders
    • Coupon collections
    • eCommerce tracker events
  • Loyalty
    • Overview
    • Set up a program
    • Enroll members
    • Credit & debit points
    • Read member data
    • Best practices
  • Custom Objects
    • Custom objects management
  • Brevo tracker and events
    • Getting started
    • JavaScript implementation
    • REST implementation
    • Legacy tracker documentation
    • Events
  • Accounts and settings
    • Senders and domains
    • User activity logs
    • External feeds
    • Invited users
LogoLogo
Help CenterAPI KeysStatusSign In
On this page
  • API key authentication
  • OAuth 2.0 authentication
Getting started

Authentication schemes

Choose between API key and OAuth 2.0 authentication for the Brevo API
Was this page helpful?
Previous

API key authentication

Generate and use an API key to authenticate your Brevo API requests
Next
Built with
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.