Send with Mailjet

To send a Mailjet newsletter from ReputeCast, you connect a Mailjet API key and its secret key. ReputeCast registers an event callback for each event it needs, sets up your sending domain, sends up to 50 messages per call with Mailjet’s tracking off, and keeps Mailjet’s campaign exclusions in step with the shared suppression list.

Kind	API
Bulk marketing	Allowed
Event webhooks	Registered by ReputeCast; basic auth in the callback URL (Mailjet doesn't sign)
Domain setup	API
Suppression sync	Two-way
Batch size	50
Notes	Mailjet allows one callback URL per event and API key, so use a key only ReputeCast uses. Suppressions sync with Mailjet's campaign exclusions.

Before you begin

• An API key and its secret key from Mailjet › Account settings › API key management. Create a key that only ReputeCast uses: Mailjet allows one callback URL per event and API key, so a key shared with another tool clashes with its callbacks.
• Permissions. Connecting needs providers:manage; adding a new sending domain needs domains:manage.
• A public HTTPS address for the callbacks: <public URL>/hooks/mailjet/<token>. Mailjet’s event API posts to the URL you give it and recommends HTTPS with basic auth credentials in the URL (Mailjet: Event API, checked October 2026), which is how ReputeCast registers it.

Connect Mailjet

1. Open Sending providers, choose Add provider and pick Mailjet in the catalog. Connect a sending provider explains the steps every provider shares.

2. Paste the API key and the Secret key. Mailjet has no API for your plan, so enter your Plan · emails per month under the extra Mailjet settings if you want a quota bar.

3. Choose Connect. ReputeCast checks the key pair with a read-only call and stores both values encrypted. The card shows whether the key is active.

4. In 2. Webhooks, ReputeCast tests its own public URL, then registers one callback for each of sent, bounce, blocked, spam and unsub. Each callback URL carries basic auth credentials (https://reputecast:<secret>@<your host>/hooks/mailjet/<token>), because Mailjet doesn’t sign its callbacks. Open and click events aren’t registered: ReputeCast tracks them itself.

5. Choose Continue to domain verification and enter your sending domain. ReputeCast adds a domain sender (*@<your domain>) in Mailjet and lists the records Mailjet wants: the ownership TXT record, DKIM and SPF (with include:spf.mailjet.com), plus DMARC if the domain has none.

6. In Test send, send a test and watch the sent callback come back as a delivery.

7. In Streams and Contacts, pick the streams and keep the option to pull Mailjet’s existing exclusions ticked.

Check that it worked

• The Mailjet card on Sending providers › , then Providers shows Healthy and “API key active”.
• In Mailjet, the event notification settings of that API key point sent, bounce, blocked, spam and unsub at your ReputeCast URL.
• Deliveries and bounces appear under Sending providers › , then Events & sync.

ReputeCast sends through Mailjet’s Send API v3.1, up to 50 messages per call, with open and click tracking disabled on each message. The monthly count on the card is what this key sent this month, read from Mailjet’s statistics.

Note

Mailjet’s exclusion list applies only to campaigns sent from Mailjet, not to the Send API that ReputeCast uses. ReputeCast checks its own suppression list before every send; the sync keeps Mailjet’s own campaigns in line with it.

Troubleshooting

• “Mailjet rejected this key” with 401 Unauthorized. The API key and the secret key come as a pair: check both, even though the error is shown on the API key field.
• “Mailjet allows one callback URL per event and API key” when registering webhooks. Another tool (or an old ReputeCast address) already uses those events on this key. Use an API key only ReputeCast uses, or remove those callbacks in Mailjet, then choose Try registering again. The events that weren’t taken are registered anyway.
• The card says “API key inactive” or “in quarantine”. Mailjet has limited the key. Sort it out in Mailjet before you route mail to it.
• The domain shows “is not set up in Mailjet”. The domain sender was deleted in Mailjet. Recreate the *@<your domain> sender in Mailjet.
• The catalog shows a “Sandbox mode” badge. ReputeCast never sends through Mailjet’s sandbox mode: every message it hands over is delivered.
• You disconnected Mailjet. ReputeCast deletes the callbacks that point at its URL. The domain sender and the exclusions stay in Mailjet.

Related

• Connect a sending provider
• Delivery events and suppression sync
• Add sending domains and senders
• Set up SPF, DKIM and DMARC
• Choose a sending provider