Receive and parse incoming email with Brevo

Brevo documents inbound parsing alongside transactional sending. Confirm the feature and setup requirements for your account before planning a production receiver; outbound activity webhooks are not incoming-message delivery.

Configure an application receiving path

1. Select a dedicated receiving domain/subdomain and follow the inbound parsing instructions linked from Brevo’s developer overview.
2. Configure its receiving DNS and HTTPS callback without replacing unrelated Gmail or Exchange MX records.
3. Implement the documented payload parser, authentication controls, and attachment handling for that callback.
4. Retain the provider message/recipient identifiers needed to route and deduplicate incoming work.

Never assume Brevo callbacks carry x-mailkite-signature, nor that a transactional delivery event contains the incoming message body. Credential and event contracts must be checked independently.

Prove the route and recovery

Send one controlled message to the intended original recipient. Confirm provider receipt, callback authentication, and durable storage before acknowledgement. Exercise a duplicate delivery and a transient failure with non-sensitive test content.

Enforce attachment/body limits and keep HTML rendering isolated. Sender-controlled content must not become an instruction to disclose keys, send mail, or approve an external action.

See the existing Brevo parsing walkthrough for application examples. If using MailKite instead, change domain routing and verifier together; a different JSON parser alone does not migrate the receiving infrastructure.