DextelDocs

Connect Mailjet

Send API v3.1 with event notifications; the Parse API (inbound) is created for you by Dextel and needs a paid plan.

Where this lives in Dextel

Agency: Agency → Integrations → Email Service (outbound only). Sub-account: Settings → Integrations → Email Integration (outbound + inbound). The modal shows the exact webhook URLs to paste into Mailjet; this page explains what to do with them.

Prerequisites

  • A Mailjet account and a domain you control (you'll add DNS records).
  • Owner or admin access to the Dextel agency or sub-account.
  • Credentials you'll enter in Dextel: API key, Secret key.

1. Create the API credentials

  1. Open Account settings → API Key Management (Primary and Sub-account) → Generate.
  2. Copy both the API key and the Secret key into Dextel.

Mailjet docs: API keys

2. Verify your sending domain

  1. Open Account settings → Sender domains & addresses → Add a domain and validate ownership.
  2. Under Manage → SPF/DKIM add the SPF TXT (v=spf1 include:spf.mailjet.com ~all) and the DKIM TXT (mailjet._domainkey).
  3. Click Check now.

Then in Dextel enter a From email on that domain (for example hello@yourdomain.com) and a From name, and click Validate & Connect. Dextel checks the credentials against Mailjet before saving.

Mailjet docs: domains

3. Delivery events

Delivered, opened, clicked, bounced and spam events feed the Email Event workflow trigger and automatically unsubscribe contacts after a hard bounce or complaint. Copy the Webhook URL from the Delivery events tab in Dextel, then:

  1. Open Account settings → Event notifications.
  2. For Sent, Open, Click, Bounce, Blocked and Spam set the URL to <your delivery-events webhook URL>. Grouped or single events both work.
  3. Keep the URL private — Mailjet doesn't sign webhooks.
This provider does not sign its webhooks. The webhook URL Dextel gives you contains a private token that authenticates each post — never share the URL.

Use Send a test email in the same tab to confirm outbound works; the events pill turns green once the first event arrives.

Mailjet docs: webhooks

4. Inbound email (sub-accounts only)

Inbound turns contact replies into Inbox conversations and fires the Contact Replied — Email trigger. Mail is received at your saved From address, so when a contact hits Reply the message comes back through Mailjet to Dextel. The MX record routes all mail for that domain to Mailjet: if you already receive mail on the domain, send from an address on a subdomain (for example hello@mail.yourdomain.com).

DNS records

TypeHostValuePriority
MXyourdomain.comparse.mailjet.com10

Steps

  1. Add an MX record for yourdomain.com pointing to parse.mailjet.com (priority 10).
  2. In Dextel's Inbound tab click Register with Mailjet — Dextel creates a Parse API route for *@yourdomain.com.
  3. Send a test email to your From address.

Registered by Dextel

Mailjet only exposes inbound configuration through its API, so the Inbound tab has a Register with Mailjet button that creates the route with your stored key once the DNS records are live.

Limits

  • The Parse API requires a paid Mailjet plan.

Mailjet docs: inbound

Troubleshooting

  • Registration returns 401/403 — the plan doesn't include the Parse API, or the key pair is a sub-account key without that permission.
  • Events arrive but none match — Dextel matches on Message_GUID; make sure you use the API key pair that sent the mail.
  • Still stuck? Compare with another provider on the Email Providers overview.