Mailjet

One Mailjet API key pair — the API key and the secret key — covers both transports: Mailway uses the pair for Mailjet’s API and as the SMTP login. Mailjet’s event notifications report what happened after the handoff — deliveries, bounces, blocks, and spam reports — which powers the delivered state, webhooks like mail.delivered and mail.bounced, and automatic suppressions.

Before you start

• A Mailjet account with your sender domain or address validated — see Deliverability for what each record proves.
• The API key and secret key: Account settings → API keys.

Add the account in Mailway

1. Add the provider.

   In the console, open Providers → New provider, pick Mailjet and paste the API key and the secret key. Mailway relays SMTP mail over in-v3.mailjet.com on port 465 (implicit TLS), and sends API and console mail over Mailjet’s API. Secrets are encrypted at rest.

   Tip

   Leave Send via on Auto. Set to API only, relayed mail can’t be handed over as-is, because Mailjet’s API is structured-only. It then skips the account unless a project admin enables re-encoding on the attachment.

2. Attach it to a project.

   Open the project, attach the provider, and position it in the failover order.

Delivery events

Without delivery events, Mailjet only reports that it accepted the mail. With them, Mailjet tells Mailway what happened afterwards.

1. Open delivery tracking. In the console, open the provider → Delivery tracking (beside Configure). Mailway creates the provider’s webhook URL. Mailjet signs nothing, so Mailway also generates a login and shows the URL with that login embedded — copy that one. It contains a secret; treat it like a password.

2. Add the events in Mailjet. Account settings → REST API → Event notifications (webhooks). Set the copied URL as the endpoint for Sent, Bounce, Blocked, and Spam (or set it on one event and use Apply url to all events). Open, Click, and Unsub can stay off — Mailway never tracks engagement. Mailjet’s Sent is its delivery confirmation; turn on Group events if you send in volume.

What each event does in Mailway

Mailjet event	Mailway outcome
Sent	The mail turns delivered (confirmed by the provider’s event: Mailjet’s Sent means the receiving server accepted it).
Bounce (hard)	The mail turns bounced; the address is auto-suppressed for the project.
Bounce (soft)	Recorded as soft_bounced (temporary; a later delivery outranks it).
Blocked	Recorded as dropped: Mailjet didn’t send it. The mail keeps its state.
Spam	The mail turns complained; the address is auto-suppressed.

Note

API sends correlate through the message id Mailjet returns. For mail relayed over SMTP, Mailway adds an X-MJ-CustomID header carrying the mail’s Mailway id, which Mailjet echoes on every event and removes before delivery. If your app sets its own X-MJ-CustomID, Mailway’s value replaces it — see What Mailway sends the provider.

Check the connection

• Connection check. The provider page’s connection check logs in over SMTP and reads your Mailjet senders, without sending anything.
• Delivery events. Mailjet’s own test button posts an empty event, so send a test email from the Delivery tracking dialog’s last step instead: it waits for Mailjet’s first event and ticks when it arrives.

What Mailjet changes

Mailjet tracks opens and clicks by default. With tracking on, Mailjet adds an open-tracking image and routes web links through its click tracker. You can turn both off in Mailjet: Account → Tracking (the setting applies to the whole account). See What providers change.

Limits

Your Mailjet plan’s own sending limits apply. Mailway adds none for Mailjet beyond your Mailway plan’s quotas.