Changelog

Apps — public apps

With Brevo CLI 2.5.0, you can create public apps: OAuth apps that any Brevo account can authorize once Brevo has reviewed and approved them. Use a public app when you offer a Brevo integration to your own customers, for example with an install link in your SaaS product or a listing on a third-party marketplace. Brevo doesn’t list public apps on a Brevo marketplace. Private apps are unchanged and remain limited to your own organization.

• Create: brevo app create --distribution public. You agree to the Brevo Developer Terms when you create the app (--accept-developer-terms in scripts). The distribution type is fixed after creation.
• Review: brevo app submit asks you to confirm the submission statement (--accept-submission-terms in scripts) and opens a submission form. Brevo emails you the decision, generally within 7 days. Track it with brevo app status.
• Withdraw: brevo app withdraw takes the app out of submission. If it was approved, that version is no longer available to Brevo accounts until you submit it again.
• OAuth: a public app uses the authorization code flow with PKCE and has no client secret.
• Limits: public apps are consent-based OAuth apps only. Machine-to-machine apps and Brevo Functions stay private, and UI apps can’t be public for now. Changing an approved app’s scopes requires a new review.

See Private and public apps and the CLI reference.

Also updated: since CLI 2.4.0, brevo app create no longer asks for a logo or accepts --logo-uri; the CLI reference now reflects this. Set logo_uri in app-config.json, then run brevo app upload.