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.


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

Request

Overview of all outbound email statistics with optional date filtering.

Domain Filtering - Use the domain_id parameter to get statistics for a specific sending domain only.

Confidence-Based Scanner Detection - Use the filter parameter to exclude bot/scanner engagement and get accurate human-only metrics.

The system now uses a confidence score (0-100) to classify engagement:

  • scanner (>= 80): Known email security systems and bots
  • suspicious (50-79): Edge cases that may be automated
  • human (< 50): Real user engagement

Gmail and Outlook Web clicks are correctly classified as "human" since these clients strip referrer headers for privacy but show other human signals (residential IP, real browser UA, normal timing).

Security
ApiKeyAuth
Query
fromdatestring(date-time)

Start date for filtering (ISO 8601)

Example: fromdate=2024-03-01T00:00:00Z
todatestring(date-time)

End date for filtering (ISO 8601)

Example: todate=2024-03-31T23:59:59Z
filterstring

Filter statistics by engagement type (NEW - Scanner Detection Feature):

  • all (default): All opens/clicks including scanners
  • human_only: Only real human engagement
  • scanner_only: Only bot/scanner engagement
Default "all"
Enum"all""human_only""scanner_only"
Example: filter=human_only
domain_idinteger

Filter statistics by specific sending domain ID

Example: domain_id=123
curl -i -X GET \
  'https://api.mailerlogic.net/api/v1/stats/outbound?fromdate=2024-03-01T00%3A00%3A00Z&todate=2024-03-31T23%3A59%3A59Z&filter=human_only&domain_id=123' \
  -H 'X-API-Key: YOUR_API_KEY_HERE'

Responses

Statistics retrieved successfully

Bodyapplication/json
sentinteger
deliveredinteger
bouncedinteger
failedinteger
opensinteger

Total opens (filtered by filter parameter)

unique_opensinteger

Unique opens (filtered by filter parameter)

clicksinteger

Total clicks (filtered by filter parameter)

human_opensinteger

NEW - Confidence-Based Detection: Opens classified as human (confidence < 50). Real user engagement excluding Gmail/Outlook image prefetch and security scanners.

scanner_opensinteger

NEW - Confidence-Based Detection: Opens classified as scanners (confidence >= 80). Known email security scanners, bots, and automated systems.

human_clicksinteger

NEW - Confidence-Based Detection: Clicks classified as human (confidence < 50). Real user clicks excluding security scanner pre-fetches.

scanner_clicksinteger

NEW - Confidence-Based Detection: Clicks classified as scanners (confidence >= 80). Automated clicks from security systems.

human_open_ratestring

Percentage of emails opened by real humans (human_opens / sent * 100)

Example: "15.50"
human_click_ratestring

Percentage of emails clicked by real humans (human_clicks / sent * 100)

Example: "8.25"
unique_clicksinteger

Unique clicks (filtered by filter parameter)

spam_complaintsinteger
trackedinteger

Total tracked events (opens + clicks, filtered by filter parameter)

Response
application/json
{ "sent": 0, "delivered": 0, "bounced": 0, "failed": 0, "opens": 0, "unique_opens": 0, "clicks": 0, "human_opens": 0, "scanner_opens": 0, "human_clicks": 0, "scanner_clicks": 0, "human_open_rate": "15.50", "human_click_rate": "8.25", "unique_clicks": 0, "spam_complaints": 0, "tracked": 0 }

Request

Daily breakdown of emails sent with optional filtering.

Use domain_id to filter statistics for a specific sending domain.

Security
ApiKeyAuth
Query
fromdatestring(date-time)

Start date for filtering (ISO 8601)

Example: fromdate=2024-03-01T00:00:00Z
todatestring(date-time)

End date for filtering (ISO 8601)

Example: todate=2024-03-31T23:59:59Z
tagstring

Filter by email tag

Example: tag=newsletter
domain_idinteger

Filter statistics by specific sending domain ID

Example: domain_id=123
curl -i -X GET \
  'https://api.mailerlogic.net/api/v1/stats/outbound/sends?fromdate=2024-03-01T00%3A00%3A00Z&todate=2024-03-31T23%3A59%3A59Z&tag=newsletter&domain_id=123' \
  -H 'X-API-Key: YOUR_API_KEY_HERE'

Responses

Send statistics retrieved successfully

Bodyapplication/json
daysArray of objects
Response
application/json
{ "days": [ {} ] }

Request

Daily breakdown of bounced emails with hard/soft bounce classification.

Use domain_id to filter statistics for a specific sending domain.

Security
ApiKeyAuth
Query
fromdatestring(date-time)

Start date for filtering (ISO 8601)

Example: fromdate=2024-03-01T00:00:00Z
todatestring(date-time)

End date for filtering (ISO 8601)

Example: todate=2024-03-31T23:59:59Z
tagstring

Filter by email tag

Example: tag=newsletter
domain_idinteger

Filter statistics by specific sending domain ID

Example: domain_id=123
curl -i -X GET \
  'https://api.mailerlogic.net/api/v1/stats/outbound/bounces?fromdate=2024-03-01T00%3A00%3A00Z&todate=2024-03-31T23%3A59%3A59Z&tag=newsletter&domain_id=123' \
  -H 'X-API-Key: YOUR_API_KEY_HERE'

Responses

Bounce statistics retrieved successfully

Bodyapplication/json
daysArray of objects
Response
application/json
{ "days": [ {} ] }

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