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.
After sending an email, the following events are tracked automatically:
Query these events via the /api/events endpoint (enterprise feature).
Failed emails are automatically retried with exponential backoff:
Retry Schedule:
After all retries are exhausted, the email status becomes failed.
Send a single transactional or marketing email via REST API.
Simple API for sending emails with:
Requirements:
Auto-domain selection: If you don't specify a domain, we'll automatically use your first verified domain.
Sending domain (optional - auto-selects first verified domain if omitted)
From email address (defaults to noreply@domain)
BCC recipients (hidden from other recipients)
Plain text email body (fallback for non-HTML clients)
Custom email headers for the message.
Use cases:
X-Order-ID, X-User-IDReply-To addressWebhook support: Headers are included in webhook payloads alongside metadata.
Note: Headers are sent with the email and included in webhooks. Use metadata for data that should NOT be sent in the email.
IP stream type for routing (default: shared)
transactional: High-priority emails (passwords, confirmations)broadcast: Marketing campaigns and newslettersshared: General purpose emailsCustom metadata (stored in database, NOT sent in email).
Use cases:
Webhook support: Metadata is included in all webhook events (delivered, bounced, opened, clicked, complained, unsubscribed).
Difference from headers: Metadata is never sent in the email, while headers are included in the email message.
File attachments (PDF, ZIP, images, documents).
Important: Attachments are sent directly through SMTP without storing on server. Base64 encode your files and include them in the request.
iCal calendar event in RFC 5545 format for meeting invites.
Native calendar support - works with Gmail, Outlook, Apple Mail:
Implementation: Sends as both text/calendar MIME alternative AND invite.ics attachment for maximum compatibility.
Important: Event is sent directly, not stored on server.
curl -i -X POST \
https://api.mailerlogic.net/api/v1/send \
-H 'Content-Type: application/json' \
-H 'X-API-Key: YOUR_API_KEY_HERE' \
-d '{
"to": "user@example.com",
"subject": "Welcome to our platform!",
"html": "<h1>Welcome!</h1><p>Thanks for signing up.</p>",
"text": "Welcome! Thanks for signing up."
}'{ "to": "user@example.com", "submitted_at": "2024-03-15T14:30:00Z", "message_id": "<550e8400-e29b-41d4-a716-446655440000@mail.yourdomain.com>", "email_id": "550e8400-e29b-41d4-a716-446655440000", "status": "queued", "message": "Email queued for delivery" }
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: