Skip to content

MailerLogic API (1.0.0)

Complete REST API for managing email delivery, tracking, and analytics.

Get started in minutes:

  1. Get your API key from your customer dashboard
  2. Send authenticated requests using the X-API-Key header
  3. Start sending emails via SMTP or API

For detailed guides, see the Getting Started section in the navigation.

Languages
Servers
US Data Center
https://api.mailerlogic.net
EU Data Center (coming soon)
https://eu-api.mailerlogic.net

Quickstart Guide

Get started with MailerLogic in minutes. This guide walks you through sending your first email.

Features Overview

MailerLogic provides enterprise-grade email delivery infrastructure with powerful APIs, deliverability optimization, and comprehensive analytics. Built by developers, for developers.


🌐 Domain Setup & Verification

Q: Why do I need to verify my domain?

Domain verification proves you own the domain and enables email authentication (SPF, DKIM, DMARC), which significantly improves deliverability and prevents spoofing.

Q: How long does DNS verification take?

DNS changes typically propagate within 1-4 hours, but can take up to 48 hours in some cases.

Q: Do I need a subdomain or can I use my main domain?

We recommend using a subdomain like mail.yourdomain.com for sending. This:

  • Isolates email reputation from your main website
  • Allows independent DNS configuration
  • Provides better tracking and organization

Q: What if my domain verification fails?

Check that:

  • All DNS records are added correctly (no typos)
  • DNS changes have propagated (can take up to 48 hours)
  • There are no conflicting SPF or DKIM records
  • Your DNS provider supports TXT records

Use the verify endpoint to see specific failure reasons.

Q: Can I use multiple domains?

Yes! You can add multiple domains to your account (based on your plan limits). Each domain has independent statistics and reputation.


✉️ Sending Emails

Q: What's the difference between SMTP and REST API?

  • REST API: Simple HTTP POST endpoint (/api/send) for sending emails with JSON payload - recommended for modern applications
  • SMTP: Standard email protocol, works with all email libraries and clients - better for legacy systems or when using existing SMTP libraries

Q: What SMTP ports do you support?

  • Port 587 (STARTTLS - recommended)
  • Port 2525 (alternative STARTTLS)
  • Port 25 is not supported
  • Port 465 (SSL) may be added in the future

Q: Can I send attachments?

Yes, attachments are fully supported via SMTP. Maximum email size including attachments is 10MB.

Q: How many recipients can I send to per email?

Maximum 50 recipients per email. For larger lists, send multiple emails or use our bulk sending features.

Q: What's the sending rate limit?

Rate limits are configurable per customer and depend on your IP type:

  • Shared IPs: Default 50 emails/second (3,000/minute, 180,000/hour)
  • Dedicated IPs: Default 500 emails/second (30,000/minute, 1.8M/hour)
  • Batch Sending: Up to 1,000 recipients per API call

These are starting defaults. Higher limits available for high-volume senders with good reputation. Contact support to increase your throughput.

Q: Why are my emails going to spam?

Common causes:

  • Domain not verified (ensure SPF, DKIM, DMARC configured)
  • Poor content (use content scoring API)
  • Low engagement rates
  • High bounce/complaint rates
  • New IP needs warm-up

📊 Tracking & Analytics

Q: How does open tracking work?

We insert a tiny invisible 1x1 pixel image in your emails. When the recipient opens the email and images load, we record the open event.

Limitations:

  • Requires images to be enabled
  • Privacy features in Apple Mail/Gmail may block tracking

Q: How does click tracking work?

We automatically rewrite all links to route through our tracking domain. When clicked, we record the event and redirect to the original URL (typically under 100ms).

Q: Can I disable tracking for specific emails?

Yes, tracking can be disabled:

  • Globally in account settings
  • Per domain
  • Per email (coming soon via API/SMTP headers)

Q: How long do you store tracking data?

  • Event data: 90 days
  • Aggregated statistics: Indefinitely
  • Detailed logs: 30 days

Enterprise plans can request extended retention.

Q: What timezone are timestamps in?

All timestamps are in UTC (Coordinated Universal Time) using ISO 8601 format: 2024-03-15T14:30:00Z


Email Sending

Send transactional and marketing emails via REST API. Simple API for sending individual emails with full tracking support.

Operations

Profile

Manage your customer profile, view usage limits, and rotate API keys. Start here to understand your account settings and available resources.

Operations

SMTP

Get SMTP credentials for sending emails directly through our mail servers. Use these endpoints to retrieve and rotate your SMTP passwords.

Operations

Sending Domains

Add and verify domains for sending authenticated emails. Configure SPF, DKIM, and DMARC records to improve deliverability.

Operations

Tracking Domains

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:

  1. Create tracking domain
  2. Add CNAME record to DNS
  3. Verify DNS configuration
  4. SSL automatically provisions (1-2 minutes)
  5. Assign to sending domains
Operations

Statistics

Access detailed email delivery and engagement metrics. Query sends, bounces, opens, clicks, and spam complaints with flexible date filters.

Operations

Content Scoring

Analyze email content for spam patterns before sending. Get actionable feedback to improve deliverability scores.

Operations

Email Validation

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.

Operations

Risk Assessment

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.

Operations

Events

🔒 Enterprise Feature - Query email lifecycle events with human engagement detection and device analytics.

Operations

Suppressions

Manage system-level suppressions for bounces and spam complaints.

Suppression Types:

  • Hard Bounces: Permanent delivery failures (automatically added by the system)
  • Soft Bounces: Temporary delivery failures (automatically added after threshold)
  • Complaints: Spam complaints and feedback loop reports

Suppression Scope:

  • Global: Applies to ALL your domains (when no domain_id specified)
  • Domain-specific: Applies to a specific domain only

Key Features:

  • Automatic bounce and complaint handling
  • Whitelist management to override suppressions
  • List all suppressions with filtering
  • Manual suppression management

Automated list hygiene to protect your sender reputation and ensure compliance.

Operations

Unsubscribes

Manage user consent and opt-out preferences.

User-Initiated Opt-Outs:

  • Unsubscribe link clicks in emails
  • API-based unsubscribe requests
  • Domain-specific or global unsubscribe preferences

Unsubscribe Scope:

  • Global: User opts out from ALL your domains
  • Domain-specific: User opts out from a specific domain only

Key Features:

  • Add emails to unsubscribe list
  • Remove (re-subscribe) emails
  • List all unsubscribed emails with filtering
  • Automatic enforcement during email sending

Ensures compliance with CAN-SPAM, GDPR, and other anti-spam regulations.

Operations

Health Score

Monitor your account's email health and engagement quality metrics. Get a 0-100 score with reputation grade (A+ to F) and actionable insights.

Operations

Tracking

Public endpoints for open and click tracking. These are called automatically by email clients - no authentication required.

Operations

Outbound Webhooks

MailerLogic sends real-time webhook notifications to your configured endpoint for all email events.

Webhook Scopes:

Customer-Level Webhooks (domain_ids = null or [])

  • Receives events from ALL domains
  • Simplest setup for single-backend applications

Single Domain Webhooks (domain_ids = [uuid])

  • Receives events from ONE specific domain
  • Useful for isolated domains

Domain Group Webhooks (domain_ids = [uuid1, uuid2, ...])

  • Receives events from MULTIPLE specific domains
  • Perfect for grouping related domains when webhook endpoint limits apply
  • Example: Plan has 20 domains, 5 webhook limit → group marketing domains, support domains, etc.

Mixed Approach

  • You can combine all three types
  • Domain-specific/group webhooks fire first, then customer-level
  • Maximize efficiency with limited webhook endpoints

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 timestamp
  • email_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:

Operations