MailerSend review

MailerSend is a hosted messaging service: your application sends email, SMS or WhatsApp messages through its API or SMTP relay, and MailerSend handles delivery. It is not a library or a server you deploy in your own infrastructure. SDKs provide client-side integration, while the service remains vendor-hosted.

In a typical stack, application code calls MailerSend when it needs to send a password reset, billing alert or other transactional message. SMTP offers an alternative for systems already configured to relay mail. Delivery tracking and webhooks let downstream services respond to email activity, while the app or MailerSend interface can verify addresses. The service also provides team controls, including role-based access control, two-factor authentication and SSO. Its stated 99.5% guaranteed uptime and 24/7 support are relevant operational claims, but teams should review the service terms and confirm which plan covers their required features before routing critical messages.

The email API uses HTTP requests: the homepage example sends a JSON payload to https://api.mailersend.com/v1/email with a bearer token. You can also send through SMTP. The homepage provides code examples for cURL, Node.js, PHP, Laravel, Python, Ruby, Go and Java, and links to API documentation. These give developers a direct route from application code to a send request without requiring a separate message broker.

Webhooks expose email activity for workflows and alerts. SMS and WhatsApp are additional messaging surfaces; WhatsApp sending uses the WhatsApp Business API. The homepage does not present a CLI workflow, so teams that depend on command-line tooling should confirm CLI support in the vendor’s documentation. The code examples establish the named languages and frameworks, but check the documentation for current package names, supported operations and feature coverage before choosing an SDK. Email verification is available through the API or app, in bulk or in real time.

The Free plan costs $0 and includes 500 emails per month, the email API and SMTP relay, email threads support and a drag-and-drop builder. The homepage also advertises a 14-day Professional trial. Hobby costs $7 monthly or $5.60 per month with yearly billing; it includes 5,000 emails monthly and 1,000 daily API requests. Starter includes 50,000 emails and 100,000 daily requests, while Professional includes 50,000 emails and 500,000 daily requests. Prices for those two plans are not published.

Extra email is $1.50 per 1,000 on Hobby and $1.30 per 1,000 on Starter and Professional. Other listed add-ons include $4 per domain space, $2 per phone number in the USA and Canada, and activity-data retention from $5. DMARC monitoring is $2 per domain. WhatsApp pricing and email-verification price per credit are not published. Enterprise pricing requires a vendor conversation. The plans have different seat, domain, template and retention limits, so compare those allowances as well as message volume.

MailerSend is a hosted service, not a self-hosted mail server. The vendor does not publish an open-source licence for the service, so teams should not treat the SDK examples as an alternative server they can run themselves. The API and SMTP relay are the integration points; applications still depend on MailerSend’s hosted delivery infrastructure.

The vendor does not publish data-export details. Before storing delivery events or verification results as business records, ask what can be exported and in which formats. Moving away is more manageable if application code calls a small internal mail adapter rather than MailerSend-specific methods throughout the codebase. SMTP can also reduce API-specific coupling for basic email sending, though it does not by itself replace MailerSend’s tracking, webhooks, SMS or WhatsApp features. Plan for a separate integration if you migrate those workflows.

The homepage states a 99.5% guaranteed uptime and 24/7 support. Treat the guarantee as a service commitment to review in the contract, not a substitute for retry logic, alerting and an alternate path for critical notifications. Daily API-request allowances range from 1,000 on Hobby to 100,000 on Starter and 500,000 on Professional. Email allowances are separate, and SMS limits differ by plan; account for both when sizing a production workload.

A Reddit thread from an operator sending about 10,000 monthly messages reports concern that suppression-list removal was not automated and says more debugging information had remained on the roadmap. That is one user’s account, not a universal service assessment, but it points to practical questions for support: how suppression changes work, what event logs expose and how long activity data is retained. Check the plan’s retention, domain and seat limits, and confirm security and compliance requirements with the vendor before routing sensitive traffic.