API tokens

This guide mirrors the API Tokens screen (Integrations → API Tokens).

What you can do here

1. Create and revoke Bearer tokens for your CRM or external system.
2. Scroll to API sends on the same page to see one-off emails accepted via POST /messages (queued, sent, or failed).
3. Filter failures from the dashboard alert or the red badge on the menu item.
4. If customers reply and nothing arrives: set Reply-To in Sending setup (or pass reply_to on POST /messages). From on the sending domain is often not a real mailbox.
5. Queue tip: pending usually becomes sent within seconds to ~2 minutes. A CRM alert at 90s is a soft warning; treat as platform incident only after ~5 minutes. On HTTP 500, log error.request_id / X-Request-Id.
6. Panel tokens (be_token_…) on a real account send real SES mail and use quota. Portal sandbox tokens (be_sandbox_…) only simulate accept — no SES.

Full curl examples and contact upsert details are in Portuguese:

Open Portuguese guide

Technical docs: docs.brenvio.com.br.