Receive email through Mailjet Parse API
Create an application-specific Mailjet parse route and handle its incoming payload without mixing it with sending feedback.
Reviewed
Mailjet’s Parse API is an incoming-message integration. Treat it separately from Send API v3.1 and outbound event callbacks; authenticating a send request does not authenticate a future POST to your receiver.
Create and secure the receiving route
- Follow the Parse API setup linked from Mailjet’s email documentation, selecting the correct account/API-key context.
- Use a dedicated parse address or approved receiving-domain configuration. Avoid an unreviewed MX change to employee mail.
- Configure a public HTTPS receiver using the documented endpoint protection and payload format.
- Map the provider’s incoming identity and recipient fields to your application, with explicit attachment/body limits.
Do not copy an outbound webhook verification scheme onto Parse without confirming it is supported. The handler must establish source trust before triggering any agent or business action.
Validate the actual incoming path
Send a controlled message to the configured address and confirm the correct route/account delivered it. Persist work before acknowledgement, deduplicate replayed notifications, and test temporary receiver failure.
Treat parsed headers, body, and attachment names as untrusted data. A message claiming to be an administrator is not authorization to change account settings or send a response automatically.
The Mailjet Parse application walkthrough provides detailed integration context. MailKite offers a different signed JSON payload; its receiving address, verifier, and retention settings must be configured independently.