Send safely with Mailjet Send API v3.1
Build a Mailjet Messages request, inspect each per-message result, and avoid exposing recipient lists across unrelated sends.
Reviewed
Use the official Mailjet client for your language and select Send API v3.1 explicitly. The basic sending reference defines a Messages array; each element contains one message’s sender, recipients, and content.
Construct a bounded message
The following is a request-shape example, not an executable send. Replace both addresses with approved real addresses when using it through the documented client:
{
"SandboxMode": true,
"Messages": [{
"From": { "Email": "sender@example.com" },
"To": [{ "Email": "recipient@example.net" }],
"Subject": "Controlled validation",
"TextPart": "Validate the message before authorizing a live send."
}]
}Remove sandbox mode only as a deliberate live-test decision. If sending unrelated users separate notifications, create separate messages; recipients placed together in To can see one another. Do not assume Mailjet automatically generates plain text from HTML.
Inspect the complete result
Check each message’s Status and recipient tracking metadata, not only the outer HTTP response. Retain applicable MessageUUID/MessageID values with the application send record. A batch can require per-message handling rather than a single success flag.
Confirm the controlled inbox and provider activity. Investigate ambiguous submission timeouts before retrying. Keep template IDs and their variables consistent with the selected API-key context.
The main Mailjet sending guide has broader application context; MailKite uses an independent request and credential contract.