Complete REST API for managing email delivery, tracking, and analytics.
Get started in minutes:
For detailed guides, see the Getting Started section in the navigation.
Q: What programming languages do you support?
MailerLogic works with any language that can speak SMTP or HTTP/REST. We provide examples in cURL, Node.js, Python, and PHP, and you can use any standard HTTP or SMTP client in your stack (Go, Java, Ruby, .NET, etc.).
Q: Do you have SDKs or libraries?
Official SDKs are coming soon. Until then you can use:
Q: What's your API rate limit?
We separate API request limits from email throughput and quotas.
API request rate limit
X-RateLimit-Limit: 600
X-RateLimit-Remaining: 543
X-RateLimit-Reset: 1733686805Email throughput limits
Daily & monthly quotas
quota_exceeded error until the limit resets or is increased.Batch sending
/api/batch and /api/bulk-sendWhy this design?
Many providers rely on strict per-request limits or return 429 for large send bursts. MailerLogic accepts your requests, queues emails internally, and sends at the correct rate for your configuration and reputation. This lets you run large campaigns reliably without manually managing backoff or throttling logic in your application.
If you need higher limits, contact support with your use case and we'll tune your configuration.
Q: Do you have a sandbox environment?
A dedicated sandbox environment is coming soon. In the meantime you can:
Q: How do I test webhooks locally?
You can use any HTTP tunneling or webhook inspection service, for example:
Point your MailerLogic webhook URL at the generated public URL while you build and debug.
Q: Can I use MailerLogic behind a firewall?
Yes. Make sure your firewall allows:
Q: What's your uptime SLA?
We target 99.9% uptime. Enterprise plans include:
Status page: https://status.mailerlogic.com
Q: Why can't I authenticate via SMTP?
Check:
/api/smtp-credentials)Q: Why are my API requests failing with 401?
Possible causes:
X-API-Key: YOUR_KEY for customer endpoints, Authorization: Bearer YOUR_KEY only for events API)Q: Why am I getting 429 errors?
You've exceeded the API rate limit (600 requests per minute). Our system returns 429 for high-frequency non-send endpoints (stats, events, etc.).
Note: /api/send and /api/batch accept and queue emails instead of returning 429, unless your account is hard-blocked or quota is exceeded.
Wait for the reset time indicated in the X-RateLimit-Reset header, or reduce your request frequency.
Q: Why aren't my opens/clicks being tracked?
Check:
Q: Why is my email still queued?
Emails may be queued due to:
Manage custom tracking domains for branded click and open tracking. Tracking domains allow you to use your own domain (e.g., track.yourdomain.com) instead of the default mailerlogic.net domain for tracking links and pixels.
Setup workflow:
Enterprise email validation API to reduce bounce rates and protect sender reputation. Real-time validation with syntax checking, domain verification, comprehensive disposable email detection, and MX record validation. Built-in intelligence to identify role accounts and suggest corrections for common typos.
Pre-send risk assessment API for Professional and Enterprise plans. Preview risk scores before sending emails to reduce bounce rates, improve deliverability, and maintain sender reputation. Get detailed risk analysis with actionable recommendations and enforcement policy insights.
Manage system-level suppressions for bounces and spam complaints.
Suppression Types:
Suppression Scope:
domain_id specified)Key Features:
Automated list hygiene to protect your sender reputation and ensure compliance.
Manage user consent and opt-out preferences.
User-Initiated Opt-Outs:
Unsubscribe Scope:
Key Features:
Ensures compliance with CAN-SPAM, GDPR, and other anti-spam regulations.
MailerLogic sends real-time webhook notifications to your configured endpoint for all email events.
Webhook Scopes:
Customer-Level Webhooks (domain_ids = null or [])
Single Domain Webhooks (domain_ids = [uuid])
Domain Group Webhooks (domain_ids = [uuid1, uuid2, ...])
Mixed Approach
Create customer-level webhook (all domains):
curl -X POST https://api.mailerlogic.net/api/v1/customer/webhooks \
-H "X-API-Key: YOUR_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"url": "https://your-app.com/webhooks/mailerlogic",
"events": ["email.delivered", "email.opened", "email.clicked", "email.bounced", "email.complained"],
"name": "Production Webhook",
"domain_ids": null,
"is_active": true
}'Create domain group webhook (multiple domains):
curl -X POST https://api.mailerlogic.net/api/v1/customer/webhooks \
-H "X-API-Key: YOUR_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"url": "https://marketing.example.com/webhook",
"events": ["email.opened", "email.clicked"],
"name": "Marketing Domains Group",
"domain_ids": [
"550e8400-e29b-41d4-a716-446655440001",
"550e8400-e29b-41d4-a716-446655440002",
"550e8400-e29b-41d4-a716-446655440003"
],
"is_active": true
}'Create single domain webhook:
curl -X POST https://api.mailerlogic.net/api/v1/customer/webhooks \
-H "X-API-Key: YOUR_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"url": "https://support.example.com/webhook",
"events": ["email.delivered", "email.bounced"],
"name": "Support Domain Only",
"domain_ids": ["550e8400-e29b-41d4-a716-446655440000"],
"is_active": true
}'All webhook events include:
event - Event type (e.g., "email.delivered", "email.opened")timestamp - ISO 8601 timestampemail_id - UUID of the email (except unsubscribe events)tag - Optional tag for filtering/grouping (if provided when sending)metadata - Optional custom metadata object (if provided when sending)Events sent to your endpoint: