Sender’s Email API lets you send transactional emails – password resets, order confirmations, alerts – with a single API call. Built for SaaS and ecommerce.
No Credit Card Required. Cancel Anytime.
Trigger emails directly from application logic through authenticated REST endpoints. The transactional email feature comes with API and SMTP access, dynamic templates, and event tracking.
Yes. The Free Forever plan includes full API and SMTP access, dynamic templates, SPF/DKIM/DMARC authentication, and TLS encryption for up to 2,500 subscribers and 15,000 emails per month. Higher tiers add unlimited webhooks, dedicated IP pools, and longer log retention.
An email API is a programming interface that lets applications send emails through HTTP requests instead of configuring a mail server. Developers use it to trigger transactional messages like password resets and verification codes directly from code. Compared to SMTP, it offers structured JSON responses, webhook events, and built-in bounce handling.
SMTP is a transport protocol that exchanges email between servers over ports 25, 465, or 587. An email API uses HTTPS and JSON, giving faster feedback, webhook events, and easier error handling. Sender supports both, so SMTP works for legacy systems and the REST API for new builds.
Send a POST request to https://api.sender.net/v2/message/send with an Authorization Bearer header containing your API token, and a JSON body specifying from (matching your verified domain), to, subject, and HTML content. Language-specific examples live in the Sender API documentation at api.sender.net.
Every Sender API response returns X-RateLimit-Limit, X-RateLimit-Remaining, and X-RateLimit-Reset headers. When the limit is exceeded, the API returns a 429 status. Use exponential backoff based on the Reset value – see API rate limits and how to handle 429 responses for retry patterns.
