Brevo M2M authentication: scope, token lifetime and account boundaries
Brevo M2M is worth reviewing for a private server-to-server integration, but it is not automatic authorization for a multi-customer product. Decide whose account the credential belongs to, what scopes it needs and how your service handles token expiry. Creating an app, obtaining a token and receiving permission to distribute an app are different stages.
New documentation, existing keys still valid
Brevo's October 6 developer notice introduces an OAuth client_credentials M2M guide and says existing API keys remain usable. The October 8 index also adds Developer Terms documentation. Those are documentation dates reviewed October 10, not proof that every account has access or that you must immediately replace existing keys. The exact supporting CLI version and this account's eligibility were not verified.Sources: Brevo — M2M announcement · Brevo — developer changelog
The M2M guide describes private use, with each credential associated with a single account. Separate your own backend integration from a tool serving multiple customers. Do not treat a working credential for one account as permission to access another customer's data or evidence that the same design is approved for external distribution.Sources: Brevo — machine to machine
Scope and expiry require explicit design
Specify the required scope deliberately. The retrieved guide says omitting scope currently grants all scopes of the app. Omission therefore cannot be assumed to mean minimal access. Map each API action to its needed permission, then check the app and requested token scopes together. A token response alone does not prove that the granted permissions match your intention.Sources: Brevo — machine to machine
The guide describes tokens lasting about one hour, with no refresh token and no immediate revocation of already issued tokens. Plan obtaining a new token and handling expiry rather than assuming an indefinite session. When reviewing secret changes, do not assume they instantly invalidate every issued token. Include the remaining token lifetime in your exposure and recovery plan.Sources: Brevo — machine to machine
A design review before credential creation
- Describe the account owner and whether the service is private or distributed to customers. Check that the CLI you intend to use supports M2M, preserving the exact version as unknown until verified. Existing API keys do not become invalid merely because the new guide exists.Sources: Brevo — M2M announcement
- Write a least-privilege scope list tied to concrete operations. Review what omitting scope would grant and what the app itself can do. Keep client secrets on the controlled backend, away from browser code and public logs; this guide does not ask you to supply credentials.
- Design token acquisition, expiry handling and secret management. Record what happens if a token expires during a job and what evidence you use to approve another attempt. Avoid treating a credential change as verified instant revocation when the guide does not support that claim.
- Compare the private single-account conditions with the separate Developer Terms before proposing a customer-facing app. Establish account and distribution authorization separately. LessWork Lab did not create an app, issue tokens, change secrets or test access for this article.Sources: Brevo — Developer Terms
Keep unspecified access and costs unknown
Brevo has an existing Free plan, but the retrieved M2M documentation did not enumerate every eligible plan or a specific M2M price. Free's existence is not proof that the feature is enabled for your account. Hosting, credential storage and maintenance costs were not quoted; this guide proposes no paid upgrade and incurred no research spend.Sources: Brevo — pricing plans · Brevo — machine to machine
No newly negotiated code, verified calendar deadline or country-specific purchasing conditions were established. Before choosing an architecture, verify actual access and read the applicable terms. A public guide and a successful app setup are insufficient evidence of permission to distribute, act for customers or receive affiliate payments in a particular country.
Two authentication questions
Does M2M replace all existing API keys? The official notice says existing keys remain available. Evaluate the design you need instead of inferring a forced migration. Account availability and the exact CLI version still require verification.Sources: Brevo — M2M announcement
Does leaving scope blank make access safer? The guide currently says it grants all app scopes. Specify the minimum needed and inspect the granted permissions. Also plan expiry: no refresh token and no immediate issued-token revocation were documented, so do not promise either behavior.Sources: Brevo — machine to machine
Official developer material reviewed October 10, 2026; no live authentication test, security outcome or ROI established. Developer Terms applicability and external distribution approval remain case-specific. Brevo's public affiliate information requires review and traffic and prohibits PPC; this applicant's CPA amount, approval, usable link, qualifying commission and Taiwan commercial payout are unknown. No affiliate CTA is included.Sources: Brevo — affiliate eligibility · Brevo — referral and promotion restrictions · Brevo — Developer Terms
Official sources
Reviewed:
- Brevo — M2M announcement
- Brevo — developer changelog
- Brevo — machine to machine
- Brevo — Developer Terms
- Brevo — pricing plans
- Brevo — affiliate eligibility
- Brevo — referral and promotion restrictions