Magic API Email
Send WordPress emails through a transactional API provider: Resend, Mailgun, Postmark, or Mailtrap. No SMTP needed.
Solid choice
Magic API Email is a solid plugin choice in 2026, with a few things worth checking first. It runs on 60+ sites, is rated 5/5 and was last updated 5 days ago, and scores 75/100 on our health check.
- Actively developed — last update 5 days ago
- Tested with the latest WordPress (7.1)
- Momentum — downloads up 505.6% vs the previous 30 days
- Small user base (60+ active installs)
- Very few reviews so far
How does it stack up?
Side-by-side on installs, updates, ratings & supportDaily downloads
Download spikes usually follow a new release — each site that auto-updates counts as a download.
Rankings
Where Magic API Email stands todayWordPress.org search rankings
Live position in the plugin search, top 100| Keyword | Position |
|---|---|
| >100 | |
| mailgun | #26 |
| postmark | #18 |
| resend | #31 |
| smtp | >100 |
Version adoption
Share of active sites per release.
Rating breakdown
★★★★★★★★★★ 5 from 1 reviews
About Magic API Email
From the official readme · v1.2.3Description
Magic API Email replaces the default WordPress email system (wp_mail()) with a direct API connection to your chosen transactional email provider. No SMTP configuration needed — just paste your API key and you’re ready to go.
Supported Providers:
- Resend — Modern email API for developers
- Mailgun — Reliable transactional email
- Postmark — Fast, deliverable transactional email
- Mailtrap — Email delivery platform with sandbox testing
- Plunk — Email API for developers
Features:
- Per-provider settings — API key, From Email, and From Name are stored independently for each provider. Switching providers never overwrites another provider’s credentials.
- Full
wp_mail()support — attachments, Cc, Bcc, Reply-To, custom headers, and HTML bodies are all passed through to your provider. - Fallback providers — if the selected provider fails, optionally try every other provider you have credentials for.
- Automatic retries — timeouts, rate limits and provider outages can be re-queued instead of losing the email.
- Background sending — optionally queue email so no page load waits for an API call.
- Logs and statistics — every attempt is recorded, with a retention window, a one-click purge, and full support for WordPress’s privacy export/erase tools.
- Test email — Send a test email directly from the settings page to verify your configuration.
- Secure — All inputs are sanitized and validated. API keys can live in
wp-config.phpinstead of the database and are never printed back into the page. - Lightweight — No dependencies, no bloat, no build step.
- Developer-friendly — Falls back to default
wp_mail()if no API key is configured, and still fires thewp_mailfilter andwp_mail_failedaction.
External services
This plugin acts as a bridge between your WordPress site and your chosen transactional email provider. By design, instead of sending emails via standard wp_mail(), this plugin sends the content of your outgoing emails via an HTTPS API request to the provider you select in the settings.
Depending on your configuration, the plugin connects to one of the following APIs:
* Resend (api.resend.com) – Terms of Service | Privacy Policy
* Mailgun (api.mailgun.net) – Terms of Service | Privacy Policy
* Postmark (api.postmarkapp.com) – Terms of Service | Privacy Policy
* Mailtrap (api.mailtrap.io) – Terms of Service | Privacy Policy
* Plunk (api.useplunk.com) – Terms of Service | Privacy Policy
What data is sent and when?
When any plugin or WordPress core feature attempts to send an email (e.g. password resets, contact form submissions, order confirmations), the data (including the recipient’s email address, sender information, email subject, and email body content) is transmitted securely to your configured provider in order to deliver the email. No data is sent if you have not configured an API key for a provider.
Installation
- Upload the
magic-api-emailfolder to the/wp-content/plugins/directory, or install the plugin through the WordPress Plugins screen directly. - Activate the plugin through the Plugins screen in WordPress.
- Navigate to Magic API Email in the WordPress admin sidebar.
- Select your email provider, enter your API key, From Email, and From Name.
- Click Save Settings.
- Use the Send Test Email section to verify everything is working.
Frequently asked questions
Which providers are supported?
Resend, Mailgun, Postmark, Mailtrap, and Plunk are currently supported.
Do I need to configure SMTP?
No. Magic API Email sends emails directly through each provider’s REST API, so no SMTP setup is required.
Will switching providers erase my other provider’s settings?
No. Each provider’s API key, From Email, and From Name are stored separately. You can switch between providers freely without losing any credentials.
Where do I get an API key?
Resend: resend.com — Create an account and generate an API key in the dashboard. Mailgun: mailgun.com — Create an account, add a sending domain, and copy the API key. Postmark: postmarkapp.com — Create a Server and copy the Server API Token. Mailtrap: mailtrap.io — Create an account and generate a sending API token. Plunk: useplunk.com — Create a project and copy the secret API key.
Can I keep my API key out of the database?
Yes. Define it in wp-config.php and it takes precedence over anything saved on the settings page: define( 'MAGIC_API_EMAIL_RESEND_KEY', 're_xxx' ); define( 'MAGIC_API_EMAIL_MAILGUN_KEY', 'key-xxx' ); define( 'MAGIC_API_EMAIL_MAILGUN_DOMAIN', 'mg.example.com' ); define( 'MAGIC_API_EMAIL_POSTMARK_KEY', 'xxx' ); define( 'MAGIC_API_EMAIL_MAILTRAP_KEY', 'xxx' ); define( 'MAGIC_API_EMAIL_PLUNK_KEY', 'sk_xxx' );
Does it support attachments, Cc, Bcc and Reply-To?
Yes, on every provider except Plunk, whose API has no attachment or Cc/Bcc support. When Plunk is selected, each Cc/Bcc address receives its own copy and any attachments are reported on the log entry instead of being dropped silently.
What happens if a send fails?
By default the failure is logged and wp_mail_failed is fired. Under Settings → Delivery & Reliability you can additionally enable fallback providers (try every other provider that has credentials saved) and retries (re-queue timeouts, rate limits and server errors, up to three attempts).
What happens if I don’t configure the plugin?
If the API key or From Email is empty, the plugin falls back to WordPress’s default email handling — no emails are lost.
Does this plugin support HTML emails?
Yes. If WordPress or another plugin sends an email with a Content-Type: text/html header, Magic API Email will send it as HTML to the provider.
Where are errors logged?
Every send attempt — successful or not — is recorded on the Logs tab of the plugin settings page, together with the provider’s error message. API errors are additionally passed to wp_trigger_error(), so they appear in the WordPress debug log (wp-content/debug.log) when WP_DEBUG_LOG is enabled in wp-config.php.
Can I stop the log table from growing forever?
Yes. Choose a retention window under Settings → Delivery & Reliability and a daily job trims anything older. There is also a Clear All Logs button on the Logs tab. Logs are exported and erased through WordPress’s own privacy tools.
Changelog
Renamed from "MagicWP Email" to "Magic API Email". If upgrading from 1.0.4 or earlier, please re-enter your API credentials after activation as the settings storage key has changed.
1.2.3
- Fix: the
wp_mail_failedaction never fired for background or retried sends, so error-monitoring plugins saw no failures once background sending was on. It now fires once per message, when delivery is finally given up. - Fix: plain-text email sent through Plunk was handed over as HTML, collapsing line breaks and turning characters like
<and&into markup. - Fix: an attachment is now checked against a size limit (20 MB, filterable with
magic_api_email_max_attachment_size) before it is read, instead of exhausting the memory limit on a file the provider would reject anyway. - New: Mailgun EU accounts are supported — define
MAGIC_API_EMAIL_MAILGUN_EUas true inwp-config.php, or filtermagic_api_email_mailgun_api_url. EU-hosted domains could not be used at all before.
1.2.2
- Enhancement: New plugin icon and banner artwork.
1.2.1
- Compatibility: Tested with WordPress 7.1.
1.2.0
- Fix: A failed send could trigger a fatal error on WordPress 6.0–6.3, because
wp_trigger_error()only exists from WordPress 6.4. The call is now guarded. - Fix: Attachments were silently dropped. They are now delivered by Resend, Mailgun, Postmark and Mailtrap; Plunk has no attachment API, so the log entry says so instead of the file vanishing.
- Fix: Cc, Bcc, Reply-To and custom headers were discarded and are now passed to the provider.
- Fix: The
wp_mailfilter was never applied, silently disabling other plugins that hook it. It now runs before the message is sent. - Fix: The
wp_mail_failedaction is now fired when a send fails, so error-monitoring plugins see failures again. - Fix: Recipients written as
Name <user@example.com>were rejected by Mailtrap. Addresses are now parsed consistently for every provider. - Fix: Plunk silently discarded all recipients after the first. Each recipient now gets its own request.
- Fix: A non-UTF-8
Content-Typecharset could produce an empty request body. Subject and body are now converted to UTF-8. - Fix: Sending a test email registered a second
pre_wp_mailcallback, which could send and log other emails in that request twice. - Fix: The Logs tab could show stale results for up to five minutes on sites using a persistent object cache.
- Feature: Fallback providers — on failure, optionally try every other provider that has credentials saved.
- Feature: Automatic retries for timeouts, rate limits and provider errors, up to three attempts.
- Feature: Optional background sending, so a page load never waits for the provider’s API.
- Feature: Log retention window with a daily cleanup job, plus a “Clear All Logs” button.
- Feature: API keys and the Mailgun domain can be defined in
wp-config.phpand are no longer printed back into the settings page. - Feature: Email logs are now covered by WordPress’s personal data export and erase tools.
- Feature: The test email can now be sent as HTML.
- Feature: Logs can be searched by recipient or subject and filtered by status and provider.
- Feature: Export the log list — with your current search and filters applied — as a CSV file.
- Feature: Long provider errors expand in place instead of being cut off at 80 characters.
- Feature: Statistics can be viewed over the last 7, 30 or 90 days as well as all time, with a daily volume chart.
- Feature: Postmark’s message stream is now configurable instead of always being
outbound. - Feature: Site Health check reporting an unconfigured provider or a run of delivery failures.
- Feature: WP-CLI commands —
wp magic-email status,test,logsandprune. - Enhancement: Admin interface redesigned to the MagicWP brand identity, and fully right-to-left aware.
- Enhancement: Network activation creates the log table on every site of a multisite install.
- Enhancement: Added
uninstall.php— deleting the plugin now removes its table, options and queued messages.
1.1.1
- Compatibility: Tested with WordPress 7.0.
1.1.0
- Feature: Email logging — every outgoing email is now recorded in a custom database table with recipient, subject, provider, status, and error details.
- Feature: Logs tab — browse all email logs with a sortable, paginated WP_List_Table on the plugin settings page.
- Feature: Statistics tab — at-a-glance dashboard showing total emails sent, success/failure counts, and per-provider usage breakdown.
- Enhancement: Admin settings page refactored into a native WordPress tabbed interface (Settings, Logs, Statistics).
- Enhancement: Sender class now captures and stores error messages for failed API requests.
For developers
Is this your plugin? Show off the numbers.
Add a live badge to your site, docs or GitHub README. It updates on its own — no account needed.
Best Magic API Email alternatives
All email plugins →FAQ
Magic API Email: quick answers
Straight answers, pulled from live WordPress.org data.
Live data from WordPress.org · checked Oct 20, 2026
Is Magic API Email free?
Yes. Magic API Email is free to download and use from the official WordPress.org plugin directory.
Is Magic API Email safe to use in 2026?
Magic API Email is a solid plugin choice in 2026, with a few things worth checking first. It runs on 60+ sites, is rated 5/5 and was last updated 5 days ago, and scores 75/100 on our health check.
How many websites use Magic API Email?
Magic API Email is active on 60+ WordPress websites and has been downloaded 1,367 times since it launched in March 2026. It was downloaded 545 times in the last 30 days.
Does Magic API Email work with WordPress 7.1?
Yes. The developer has tested Magic API Email up to WordPress 7.1.3, the latest release. It requires WordPress 6.0 or newer.
What PHP version does Magic API Email need?
Magic API Email requires PHP 8.0 or higher. Most hosts run PHP 8.x today, so it works on any modern WordPress hosting.
When was Magic API Email last updated?
The latest version, 1.2.3, was released on October 15, 2026 (5 days ago).
Who makes Magic API Email?
Magic API Email is developed and maintained by MagicWP.io.
What are the best alternatives to Magic API Email?
The most popular alternatives to Magic API Email are WP Mail SMTP by WPForms (4M+ installs), MC4WP: Mailchimp for WordPr… (1M+ installs) and Easy WP SMTP (500K+ installs).
Powered by PageForge
Want thousands of pages that rank like these? Build them in an afternoon.
This directory runs on the same engine as PageForge. Turn any spreadsheet, CSV or API into thousands of fast, SEO-ready WordPress pages — with schema, internal links and AI-written copy baked in.
- CSV, Google Sheets & API data sources
- AI content, schema & internal links per page
- Works with Elementor, Gutenberg, Yoast & Rank Math
- Free on WordPress.org — no credit card

