Error with doubleOptinConfirmation API

What to do

• Check whether you use Brevo in us. Check your stack

  Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.

• Confirm your retries, queues and scheduled jobs caught up after the 2h 11m it lasted.

  Anything that failed between 2026-10-26 05:31 UTC and 2026-10-26 07:41 UTC may need a replay.

• Subscribe to Brevo's feed to hear about the next one first. RSS feed

  https://down.guide/feed?provider=brevo works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from Brevo 3

1. identifiedOct 26, 2026, 5:31 AM UTC

   Clients making requests to POST /v3/contacts/doubleOptinConfirmation may encounter the following error: `Your SMTP account needs to be activated to use this endpoint. Please contact us at [contact@sendinblue.com](mailto:contact@sendinblue.com "contact@sendinblue.com") to request activation.` To use the doubleOptinConfirmation endpoint, the API key must have the "Transactional Email" scope, as sending the double opt-in confirmation email is part of the flow. Only the doubleOptinConfirmation endpoint is impacted. We’re also working on improving the error message to make it more descriptive and actionable. Additionally, we’ll review the overall flow to identify opportunities to make it clearer and more intuitive for clients.

   provider

2. identifiedOct 26, 2026, 6:56 AM UTC

   We’ve updated the error message to make it clearer and more intuitive for clients. We’re also working on improving the flow to remove the dependency on the Transactional Email scope.

   provider

3. resolvedOct 26, 2026, 7:41 AM UTC

   We’ve updated the error message to make it clearer and more intuitive for clients. The API requests should not be blocked after following the recommended step in the error message.

   provider

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.