Sharraxaad
Send transactional and marketing emails from your WordPress site using the Lettr email API. Lettr replaces the default WordPress email system with a reliable, developer-friendly API that delivers emails to inboxes — not spam folders.
Why Lettr?
- Reliable email delivery — Built on battle-tested infrastructure with SPF, DKIM, and DMARC authentication out of the box.
- Simple setup — Connect your WordPress site with a single API key. No SMTP configuration needed.
- Transactional email at scale — Send password resets, order confirmations, notifications, and more through the Lettr email API.
- Real-time tracking — Monitor opens, clicks, bounces, and deliverability from the Lettr dashboard.
- Templates & personalization — Use the Lettr drag-and-drop editor and merge tags for dynamic content.
- Developer-first — RESTful API, detailed documentation, and SDKs for PHP, Node.js, Python, Go, Rust, Java, and Laravel.
How it works
This plugin overrides the default WordPress wp_mail() function and routes all outgoing emails through the Lettr API. This means every email your site sends — including emails from WooCommerce, contact form plugins, and any other plugin — is delivered through Lettr automatically.
Links
External services
This plugin connects to the Lettr API at app.lettr.com to deliver email on behalf of your WordPress site. Each time wp_mail() is invoked, the plugin sends the following data to Lettr over HTTPS so that Lettr can process and deliver the message:
- The configured sender email address and name
- Recipient, CC, BCC, and Reply-To addresses
- The email subject, HTML and/or plain text body, and any attachments
- Any custom email headers, tags, or metadata supplied by the calling code
- Your Lettr API key (sent as a Bearer token in the
Authorizationheader for authentication)
The plugin also calls app.lettr.com/api/auth/check to validate the API key when you save it on the settings screen.
This service is provided by Lettr. By using this plugin you agree to Lettr’s terms and acknowledge their privacy practices:
- Terms of Service: https://lettr.com/terms
- Privacy Policy: https://lettr.com/privacy-policy
Rakibaad
- Upload the plugin to
/wp-content/plugins/lettror install via the WordPress plugin installer. - Activate the plugin through the Plugins menu.
- Go to Settings Lettr and enter your API key from the Lettr dashboard.
- Configure your sender name and email address.
- Send a test email to verify everything is working.
SBI
-
Do I need a Lettr account?
-
Yes. Sign up for free at lettr.com to get your API key.
-
Does this work with WooCommerce?
-
Yes. Lettr handles all emails sent via the standard WordPress
wp_mail()function, which includes WooCommerce order confirmations, shipping notifications, and customer emails. -
Do I need to configure SMTP?
-
No. Lettr uses a REST API instead of SMTP, which means there are no ports to open or SMTP credentials to manage.
-
Where can I find my API key?
-
Log in to your account at lettr.com and navigate to the API Keys section.
Dibu-eegisyo
Ma jiraan wax dibu-eegis ah oo ku saabsan kaabahan.
Ka-qaybgalayaasha & Horumariyayaasha
“Lettr – Email API” waa softiweer il furan. Dadka soo socda ayaa wax ku biiriyay kaabahan.
Ka-qaybgalayaasha
Ku tarjun “Lettr – Email API” luqaddaada.
Ma xiisaynaysaa horumarinta?
Baadh koodka, fiiri bakhaarka SVN, ama iska qor diiwaanka horumarinta adigoo adeegsanaya RSS.
Isbeddellada
1.3.0
- Add bulk topic subscription API client methods (
bulk_subscribe_audience_contacts_to_topics,bulk_unsubscribe_audience_contacts_from_topics). bulk_create_audience_contacts()now documents the per-contactcontactsrequest shape, the batch-widelist_ids/topics/update_existingoptions, and theupdated/error_count/errors/contactsresponse fields. No call signature changed — existing payloads send exactly as before.- Behaviour change from the Lettr API: creating a contact whose email already exists now returns HTTP 409, so
create_audience_contact()fails with aWP_Errorcode oflettr_api_resource_already_exists(status 409). It previously returned HTTP 500, i.e.lettr_api_send_error(status 500). Custom code branching on the old code no longer matches, and a 409 here must not be retried.
1.2.0
- Add campaigns API client methods (list, show, events, send, schedule, unschedule).
1.1.0
- Add audience API client methods (lists, contacts, topics, properties, segments).
- Bump tested-up-to to WordPress 7.0.
1.0.0
- Initial release.