What authentication does the Brevo Email API use?

The Brevo Email API uses an API key passed in the 'api-key' header with each request. Through Jentic, your Brevo API key is stored encrypted in your Jentic One instance. Agents receive scoped access tokens so the raw key never enters the agent's context.

Can I send emails with dynamic templates using the Brevo Email API?

Yes. POST to /smtp/email with a templateId field and a params object containing your variable values (e.g., first_name, order_id). Brevo renders the template server-side with your parameters before delivery. Templates are managed via GET and POST /smtp/templates.

What are the rate limits for the Brevo Email API?

Brevo enforces sending limits based on your plan. Free plans allow 300 emails per day. Paid plans start at 20,000 emails per month with no daily limit. The API itself allows multiple concurrent requests but will return 429 status when plan sending limits are reached.

How do I track email delivery status through Jentic?

Search Jentic for 'check email delivery status' to find the GET /smtp/emails/{uuid} operation. Each sent email returns a messageId UUID that you can use to query delivery status including whether it was delivered, opened, clicked, or bounced. Install with pip install jentic and use the search-load-execute flow.

How do I clean hard-bounced contacts from my sending list?

Use DELETE /smtp/deleteHardbounces to purge all contacts that have permanently bounced. To review before deleting, first call GET /smtp/blockedContacts to see the full list of blocked addresses with their block reason and date. Regular cleanup prevents deliverability issues from accumulating invalid addresses.

Can I retrieve per-message event logs with the Brevo Email API?

Yes. GET /smtp/statistics/events returns event-level logs including deliveries, opens, clicks, bounces, and spam reports. Filter by date range, event type, or email address. For individual message tracking, GET /smtp/emails/{uuid} returns the full event history for a specific email by its UUID.

Can I limit what my agent is allowed to do with the Brevo Email API?

Yes. Brevo's transactional endpoints carry their target in the request body and query rather than as a resource id in the URL path, so scoping is operations-only: because Jentic One runs self-hosted, your own rules decide which Brevo operations the agent may call. You can allow it to send a transactional email and read delivery events and statistics while withholding a destructive operation such as deleting hard bounces at /smtp/deleteHardbounces, which stays off unless you add it. Your API key is injected only at execution time, so the agent never sees the raw credential.