whats-best.ai
Search Sign in

Transactional Email

Mailjet Email API

EU-Made Report an error

Panel rating · 6 judges · How to read the stars

Category median

Sovereignty: not determined

0–5 in half steps. 5 means the rubric's top anchor is met on the evidence.

by Mailjet SAS · www.mailjet.com

Compare with Brevo Transactional Email → Report an error on this page Is this your product? →

Link to this page

Mailjet Email API: AI-assisted analysis on whats-best.ai Mailjet Email API: AI-assisted analysis on whats-best.ai (dark)

Add ?theme=dark to the image address for dark backgrounds. The badge shows the category and the month of the latest evaluation, and EU-Made where that is the product’s provenance. It never shows a score.

Mailjet Email API at a glance

Vendor
Mailjet SAS
Headquarters
Not stated on the vendor’s pages as of 1 Nov 2026
Data hosting
Default not stated; pages mention United States, Europe and the EU source, captured 1 Nov 2026
Free plan
Yes, per the vendor’s own page source, captured 1 Nov 2026
Panel verdict
The AI panel rates Mailjet Email API 3/5, the mean of 6 judges. Mailjet Email API, sold by Mailjet SAS of Paris under Sweden's Sinch group, is a transactional email service with weighted totals of 6.1 to 6.3. how scores are made
As of
Vendor pages captured 1 Nov 2026; evaluated by the panel 1 Nov 2026. all sources

Mailjet Email API alternatives, European ones first →

Read this page as one judge. Each weighs the same scores by what they care about.

The SaaS Developer

Weighted verdict

Backend developer at a twelve-person B2B SaaS in Hamburg, built on Laravel, that sends sign-up confirmations, password resets, invoices and weekly digests to 40,000 users. Has replaced the mail driver once already and does not want to again. Wants an official driver for the framework, templates with variables, a test mode that never reaches a real inbox, signed webhooks for bounces, and a log that answers "did this user get the reset mail?" without opening a ticket.

Same scores as the panel view — this lens weights them the way this judge cares.

Scored by The SaaS Developer

Panel median The SaaS Developer This judge’s scores over the panel median. Each label opens its reasoning below.
Scores per criterion, in stars out of 5
Criterion Panel median The SaaS Developer
Sending API, SMTP & developer experience 3 of 5 3 of 5
Deliverability & sender reputation 3 of 5 3 of 5
Message logs, events & webhooks 3 of 5 3 of 5
Message data, retention & security 3 of 5 3 of 5
Reliability, accounts & support 3.5 of 5 3.5 of 5
European sovereignty 3.5 of 5 3.5 of 5
Pricing transparency 2.5 of 5 3 of 5

Sending API, SMTP & developer experience

How this is scored

How an application sends mail: a REST API and an SMTP relay with their limits stated, official SDKs and drivers for named languages and frameworks (PHP and Laravel, Node, Python, Ruby and Rails, Java, Go, .NET), stored templates with variables and versions, batch sending, attachments, idempotency keys, scheduled sending, a test or sandbox mode that does not deliver, inbound email parsed into a webhook, and the quality of the API reference and guides.

0 — Not a sending service; an application cannot send email through it by API or SMTP.

3 — An API or SMTP credentials to send a message; SDKs, templates, limits and a test mode are basic or not described.

5 — A documented REST API and SMTP relay, official SDKs for several named languages, stored templates with variables, attachments and batch sending, rate limits stated, a sandbox or test mode, and quick-start guides for named frameworks.

8 — An API reference with every endpoint and error code, idempotency keys, scheduled sending, template versions and a template language documented, inbound email parsed to a webhook, an OpenAPI specification or official CLI, framework drivers maintained by the vendor, and a migration guide from named competitors.

10 — An API a team builds its product on: versioning and deprecation policy published, backward compatibility stated, full parity between API and SMTP features, local or staging test tooling that mirrors production, and every limit, timeout and retry behaviour documented.

Report an error

The SaaS Developer

The REST send API and SMTP relay are both documented — ports 25, 465, 587 and 2525, a 25MB per-message ceiling, libraries for PHP, Ruby, Python, C#, Java and Node, stored templates with variables, loops and conditionals, scheduled sending, and an inbound Parse API delivering parsed headers, content and attachments to a callback URL — and the developer site carries an endpoint-level API reference. What holds me back: we found no public information on a sandbox or test mode, idempotency keys, an OpenAPI specification or CLI, a vendor-maintained Laravel driver, or a migration guide from named competitors. 1 3 5 8 11 12

Report an error

Deliverability & sender reputation

How this is scored

What the vendor does so the mail reaches the inbox: guided SPF, DKIM and DMARC set-up with a custom return path and tracking domain, shared IP pools and how senders on them are vetted and policed, dedicated IPs with automatic warm-up, transactional and bulk mail kept on separate streams or IP pools, bounces, complaints and unsubscribes turned into suppressions automatically, feedback loops with mailbox providers, blocklist and DMARC monitoring, compliance with the Gmail and Yahoo bulk-sender rules, and published delivery times or inbox placement with their method.

0 — No sender authentication and no bounce handling; mail goes out from shared addresses with no reputation management at all.

3 — SPF and DKIM can be set up and bounces are recorded; IP policy, stream separation and suppressions are basic or not described.

5 — Guided SPF, DKIM and DMARC set-up with a custom return path, shared IPs with a stated sender vetting policy, dedicated IPs available, automatic suppression of hard bounces and complaints, transactional and marketing mail separated by stream or IP pool, and deliverability guidance in the documentation.

8 — Dedicated IPs with automatic warm-up and pool management, a stated acceptable-use and vetting process for shared pools, feedback loops and blocklist monitoring, DMARC reports, BIMI or custom tracking domains, compliance with the Gmail and Yahoo sender requirements stated, delivery times published, and access to deliverability experts.

10 — Deliverability that can be verified: delivery time and bounce rates per mailbox provider published continuously with their method, inbox placement testing included, pool reputation shown to the customer, and a documented escalation path with mailbox providers.

Report an error

The SaaS Developer

SPF, DKIM and DMARC set-up is documented with DNS walkthroughs, dedicated IPs come with a support-built warm-up plan and per-IP volume management, CSA accreditation has been held since 2014, and deliverability experts, consulting calls and (on the top tier) blocklist monitoring are on offer. Separating transactional from marketing traffic is left to customers to arrange via sending addresses, sub-accounts or custom headers, and we found no public information on shared-IP vetting, feedback loops, Gmail and Yahoo bulk-sender compliance, or published delivery and inbox-placement figures. 2 4 6 10 13 14

Report an error

Message logs, events & webhooks

How this is scored

What the team can see about each message once the application has handed it over: a message log searchable by recipient, subject, tag or message ID, the full event history (processed, delivered, deferred, bounced with the remote server's answer, opened, clicked, complained), how long logs and message content are kept, event webhooks with retries and a signature, an events API, dashboards and statistics per stream, tag or domain, alerts on bounce or complaint spikes, and access for a support team without developer rights.

0 — Nothing can be seen after sending; no logs, no events and no webhooks.

3 — Totals of sent and bounced messages; per-message logs, webhooks and retention are basic or not described.

5 — A searchable message log with per-message event history and the bounce reason, log retention stated, event webhooks for delivery, bounce, open, click and complaint, statistics per tag or domain, and an API to fetch events.

8 — Webhooks signed and retried with their schedule documented, the raw SMTP response and the rendered message viewable per send, log retention configurable or extended by plan, alerts on bounce, complaint or delivery-time thresholds, export or streaming of events to a named log or data tool, and read-only roles for support staff.

10 — Full traceability: every message traceable from API call to the receiving server's final answer, events streamed in real time with ordering and delivery guarantees stated, long retention with search across the whole history, and observability features documented with their limits.

Report an error

The SaaS Developer

Every message gets detailed logs with status history, webhooks push open, click, bounce and block events in real time with endpoints configurable per event type by UI or API, and events can be pulled or streamed into Amazon SQS or Google Pub/Sub — enough for my bounce handling and to answer whether a given user received the reset mail. But we found no public information on webhook signatures or retry schedules, log retention, per-message bounce reasons with the server's answer, threshold-based alerts, or read-only access for support staff. 1 3 6 15 20

Report an error

Message data, retention & security

How this is scored

What is stored about each message and what the customer controls: whether message bodies are stored or only metadata, retention periods and the setting to shorten them, deletion of a recipient's data on request, open and click tracking that can be switched off per stream or message, TLS for delivery with an option to require it, encryption at rest, API keys with scopes and per-domain restrictions, IP allow-listing, two-factor authentication and SSO for the dashboard, an audit log, a vulnerability disclosure programme, and security certifications or audits with their scope. Where the data is processed and by whom is scored under sovereignty.

0 — Stores every message indefinitely with no controls, and the vendor states it uses message content for its own purposes.

3 — A privacy policy and a statement that data is encrypted; what is stored, retention and access controls are basic or not described.

5 — What is stored per message documented, retention periods stated, open and click tracking switchable, TLS used for delivery, API keys with restricted permissions, two-factor authentication for the dashboard, and a data processing agreement offered.

8 — Message content retention configurable down to none or metadata only, enforced TLS per domain or message, encryption at rest stated, scoped API keys and IP allow-listing, SSO (SAML) and roles, an audit log, deletion of recipient data by API, and ISO 27001 or SOC 2 stated with its scope.

10 — Data minimisation that can be verified: every stored field and its retention listed, content never stored unless the customer opts in, customer-managed encryption keys or equivalent, independent audits published with their scope, and every security control the customer has listed with its effect.

Report an error

The SaaS Developer

Message content is stored encrypted, with AES-256 minimum at rest and TLS 1.2 or higher in transit, open and click tracking can be made anonymous or consent-based, ISO 27001, ISO 27701 and SOC 2 are claimed, there is a HackerOne bug bounty, a published DPA with standard contractual clauses, deletion within ninety days of termination, and tooling for data-subject requests. Delivery TLS can fall back to unencrypted when the recipient side cannot do TLS, and we found no public information on two-factor authentication, SSO, scoped API keys, IP allow-listing or an audit log. 7 8 9 10 20

Report an error

Reliability, accounts & support

How this is scored

Whether the platform can be relied on and run by a team: a public status page with incident history, uptime SLA and service credits published, redundancy or failover across data centres described, queueing and retry of mail during outages, sub-accounts or servers per application, client or tenant, team members with roles, separate environments, support channels and response times per plan, named migration help, and integrations with platforms that send mail on the customer's behalf (WordPress, Shopify, Shopware, Supabase, Vercel and similar).

0 — No status page, no support channel and no way to separate users or applications.

3 — A support contact and a single account; status page, SLA, sub-accounts and roles are basic or not described.

5 — A public status page with incident history, an uptime SLA on at least one plan, sub-accounts or separate servers per application, team members with roles, support by email or chat with stated hours, and plugins or guides for several named platforms.

8 — An SLA with service credits published, redundancy across data centres or regions described, mail queued and retried during incidents, sub-accounts with their own keys, domains and limits manageable by API, granular roles, support response times per plan, and migration assistance offered.

10 — Reliability that can be verified: uptime history published for years, post-mortems for incidents, multi-region failover documented, an SLA covering delivery latency as well as API availability, and white-label or reseller tooling for agencies and platforms.

Report an error

The SaaS Developer

There is a published SLA at 99.99% for the API, SMTP and outbound delivery with 5% service credits per thirty minutes of downtime capped at 50% of monthly fees, a status page for unexpected interruptions, infrastructure spread over two EU regions and six data centres, queueing so mail survives server problems, daily backups, sub-accounts from the Starter plan upward, team management with advanced permissions, and ticket support with phone hours for the Americas and APAC. We found no public information on support response times per plan or plugins for platforms that send mail on your behalf, like WordPress or Shopify. 6 9 10 17 19 20

Report an error

European sovereignty

How this is scored

Who the contracting entity and the parent company are, where messages, logs and recipient data are processed and stored, whether an EU region can be chosen and what it covers, and who the subprocessors are (cloud hosting, sending infrastructure, logging, support and payment tools). Independently sourced by the sovereignty pipeline; every message carries personal data, so the whole sending chain counts, not only the dashboard.

0 — Non-EU vendor and contracting entity, hosting unstated, subprocessors unnamed, and no data processing agreement offered.

3 — A privacy policy and a data processing agreement exist, but hosting location is unstated or non-EU and the subprocessors are not listed.

5 — An EU region available and an EU contracting entity or EU representative, but parts of the chain (sending infrastructure, logs, support, payment) run through non-EU providers without a stated safeguard, or the EU region does not cover logs and account data.

8 — EU processing of messages, logs and account data on named infrastructure, an EU contracting entity, subprocessors listed with their locations, a data processing agreement published, and security certifications (ISO 27001, SOC 2) stated.

10 — Sovereign end to end and evidenced: European ownership, entity, hosting, sending infrastructure and every subprocessor, data export and deletion documented, and certifications published with their scope rather than implied.

Report an error

The SaaS Developer

The vendor's own pages state storage and processing in the EU — Google Cloud data centres in Frankfurt and Saint-Ghislain, two regions and six data centres in Europe — under a French contracting entity (Mailjet SAS, French law, Paris courts) inside the Swedish-listed Sinch group, with a published DPA incorporating the 2021 standard contractual clauses and ISO 27001/27701 certifications. Sub-processors are named — Stripe and Authorize.net for payments, Zendesk, Salesforce, Snowflake and others for support and engagement — but without their locations, and the group privacy notice describes hosting in the United States or Europe depending on where services are deployed, so I cannot call the whole chain end-to-end European. 7 8 9 10 18 20

Report an error

Pricing transparency

How this is scored

Whether a buyer can compute the real annual cost from public pages alone: price per tier by monthly message volume, the price per additional thousand messages, the free tier and its limits, what dedicated IPs, extra log retention, sub-accounts, SSO and support plans cost, minimum term, and whether unused volume carries over.

0 — No public prices at all; every customer is a sales call.

3 — A starting price or a free tier exists, but how cost scales with volume or which features cost extra is unclear.

5 — Tiers are public with their monthly volume and price, but at least one commonly needed piece (overage rate, dedicated IP, longer log retention, SSO, support plan) is unpriced or "on request".

8 — Every tier priced publicly with its volume and overage rate per thousand messages, dedicated IPs and add-ons priced, log retention per tier stated, minimum term and VAT treatment stated.

10 — Complete price computability: annual cost derivable for a given monthly volume, number of domains and sub-accounts and feature set, with every add-on, support and overage fee and the cancellation terms published.

Report an error

The SaaS Developer

Four self-service tiers are public with volume and price — free at $0 for 6,000 emails a month (200 a day), Starter at $9/month for 8,000, Essential at $19/month and Premium at $29/month for 15,000 each — with the basis stated (emails sent, not contact count), no setup fees, a one-month rolling self-service term, prices excluding French VAT with an EU VAT-number exemption, and the clear statement that unused credits expire each month. Dedicated IPs are 'upon request' and enterprise plans are sales conversations, the pricing page points to a price per additional 1,000 emails without giving the figure on the pages we read, and we found no public information on what longer log retention, SSO or support plans cost. 1 6 8 14

Report an error

European sovereignty — proven facts

0 of 6 dimensions proven

Built only from facts shown on the vendor's own pages. A dimension we could not prove is left open, not scored as zero.

Hosting location Not determined ⚠ unverified — uncited Report an error
Hosting options Not determined ⚠ unverified — uncited Report an error
Open source Not determined — uncited Report an error
Data processing agreement Not determined ⚠ unverified — uncited Report an error
Transfer impact assessment Not determined — uncited Report an error

Questions about Mailjet Email API

Is Mailjet Email API European?

Yes. whats-best.ai classifies Mailjet Email API as EU-Made.

Where does Mailjet Email API store data?

The default storage location for customer data is not stated on the vendor’s pages as of 1 Nov 2026. The vendor’s pages mention United States, Europe and the EU as hosting locations, per the vendor’s page captured 1 Nov 2026.

Does Mailjet Email API have a free plan?

Yes. Mailjet Email API has a free plan, per the vendor’s page captured 1 Nov 2026.

What are the best alternatives to Mailjet Email API?

As of 2 Nov 2026, the panel rates Lettermint (3.5/5), Bird Email API (formerly SparkPost) (3/5) and Postmark (3/5) highest among the other 15 Transactional Email products evaluated. Ratings that look equal are rounded to half stars; the order uses the unrounded rating, then the name. The highest-rated European alternative is Lettermint (EU-Made). Ratings are the AI panel’s opinion, formed from public evidence: how scores are made. The full list, with European products first: Mailjet Email API alternatives.

Where this could be wrong

What we left out

A claim that does not survive our checks costs us the claim, not the page. This is what was taken off this one.

Do you know more about Mailjet Email API? Tell us Report an error on this page

Sources (20)

The pages every claim on this page was read from — each one checked, dated, and kept verifiable.

  1. 1 Vendor homepage (email API) www.mailjet.com Checked 1 Nov 2026 Details →
  2. 2 Features page (SMTP relay) www.mailjet.com Checked 1 Nov 2026 Details →
  3. 3 Features page (transactional email) www.mailjet.com Checked 1 Nov 2026 Details →
  4. 4 Features page (deliverability) www.mailjet.com Checked 1 Nov 2026 Details →
  5. 5 API documentation dev.mailjet.com Checked 1 Nov 2026 Details →
  6. 6 Pricing page www.mailjet.com Checked 1 Nov 2026 Details →
  7. 7 Privacy policy www.mailjet.com Checked 1 Nov 2026 Details →
  8. 8 Terms of service www.mailjet.com Checked 1 Nov 2026 Details →
  9. 9 Data processing agreement (dpa) sinch.com Checked 1 Nov 2026 Details →
  10. 10 Security / trust page www.mailjet.com Checked 1 Nov 2026 Details →
  11. 11 Sending API, SMTP & developer experience — found from sitemap www.mailjet.com Checked 1 Nov 2026 Details →
  12. 12 Sending API, SMTP & developer experience — found from sitemap www.mailjet.com Checked 1 Nov 2026 Details →
  13. 13 Deliverability & sender reputation — found from sitemap www.mailjet.com Checked 1 Nov 2026 Details →
  14. 14 Deliverability & sender reputation — found from sitemap www.mailjet.com Checked 1 Nov 2026 Details →
  15. 15 Message logs, events & webhooks — found from sitemap www.mailjet.com Checked 1 Nov 2026 Details →
  16. 16 Message logs, events & webhooks — found from sitemap www.mailjet.com Checked 1 Nov 2026 Details →
  17. 17 Message data, retention & security — found from sitemap www.mailjet.com Checked 1 Nov 2026 Details →
  18. 18 Message data, retention & security — found from sitemap www.mailjet.com Checked 1 Nov 2026 Details →
  19. 19 Reliability, accounts & support — found from sitemap www.mailjet.com Checked 1 Nov 2026 Details →
  20. 20 Reliability, accounts & support — found from sitemap www.mailjet.com Checked 1 Nov 2026 Details →