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

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

Request

Retrieve your unsubscribe list with filtering and search capabilities.

Use this to:

  • Monitor user opt-out trends
  • Export unsubscribe lists for compliance
  • Audit unsubscribe sources (API, link clicks, manual)
  • Filter by domain or view all unsubscribes
  • Track consent management across your domains

Complete unsubscribe lifecycle management with comprehensive analytics and compliance reporting.

Each unsubscribe includes a scope field indicating whether it's global (all domains) or domain-specific.

Note: For system-managed suppressions (bounces, complaints), see the /api/v1/customer/suppressions endpoints.

Security
ApiKeyAuth
Query
pageinteger>= 1
Default 1
limitinteger[ 1 .. 100 ]
Default 50
searchstring

Search by email address (partial match)

domain_idstring(uuid)

Filter by specific domain (omit to see all unsubscribes)

from_datestring(date)

Filter from date (YYYY-MM-DD)

to_datestring(date)

Filter to date (YYYY-MM-DD)

curl -i -X GET \
  'https://api.mailerlogic.net/api/customer/unsubscribes?page=1&limit=50&search=string&domain_id=497f6eca-6276-4993-bfeb-53cbbbba6f08&from_date=2019-08-24&to_date=2019-08-24' \
  -H 'X-API-Key: YOUR_API_KEY_HERE'

Responses

Unsubscribes retrieved successfully

Bodyapplication/json
unsubscribesArray of objects(Unsubscribe)
paginationobject(Pagination)
Response
application/json
{ "unsubscribes": [ {}, {} ], "pagination": { "page": 1, "limit": 50, "total": 25, "pages": 1 } }

Request

Add an email address to your unsubscribe list for user consent management.

Unsubscribe Scope:

  • Global: Omit domain_id to unsubscribe from ALL your domains
  • Domain-specific: Include domain_id to unsubscribe from a specific domain only

Use cases:

  • Processing manual unsubscribe requests (phone, email, support tickets)
  • Honoring opt-out preferences from other channels
  • Importing unsubscribe lists from other platforms
  • Domain-specific opt-outs for users who want targeted unsubscribes
  • Proactive consent management

Note: Unsubscribe links in emails are handled automatically. Use this endpoint for opt-outs from other channels.

Security
ApiKeyAuth
Bodyapplication/jsonrequired
emailstring(email)required

Email address to unsubscribe

Example: "user@example.com"
domain_idstring(uuid)

Optional - Specify domain ID for domain-specific unsubscribe. Omit for global unsubscribe.

Example: "123e4567-e89b-12d3-a456-426614174000"
reasonstring

Optional reason for unsubscribe

Example: "User requested removal"
curl -i -X POST \
  https://api.mailerlogic.net/api/customer/unsubscribes \
  -H 'Content-Type: application/json' \
  -H 'X-API-Key: YOUR_API_KEY_HERE' \
  -d '{
    "email": "user@example.com",
    "domain_id": "123e4567-e89b-12d3-a456-426614174000",
    "reason": "User requested removal"
  }'

Responses

Email unsubscribed successfully

Bodyapplication/json
messagestring
Example: "Email unsubscribed successfully"
unsubscribeobject(Unsubscribe)
Response
application/json
{ "message": "Email unsubscribed successfully", "unsubscribe": { "id": "string", "email": "user@example.com", "source": "link", "reason": "string", "created_at": "2019-08-24T14:15:22Z" } }

Request

Remove an email from your unsubscribe list, allowing them to receive emails again.

Re-subscribe Scope:

  • Global: Omit domain_id query param to remove from global unsubscribe list
  • Domain-specific: Include domain_id query param to remove domain-specific unsubscribe

Important: Only do this when:

  • The recipient has explicitly requested to be re-subscribed
  • You have documented proof of their consent
  • You comply with applicable consent regulations (GDPR, CAN-SPAM, etc.)

Use cases:

  • Processing re-subscription requests from users
  • Honoring preference center updates
  • Correcting accidental unsubscribes
Security
ApiKeyAuth
Path
emailstring(email)required

Email address to re-subscribe (URL encoded)

Query
domain_idstring(uuid)

Optional - Specify domain ID to remove domain-specific unsubscribe. Omit to remove global unsubscribe.

curl -i -X DELETE \
  'https://api.mailerlogic.net/api/customer/unsubscribes/{email}?domain_id=497f6eca-6276-4993-bfeb-53cbbbba6f08' \
  -H 'X-API-Key: YOUR_API_KEY_HERE'

Responses

Email re-subscribed successfully

Bodyapplication/json
messagestring
Example: "Email re-subscribed successfully"
emailstring(email)
Response
application/json
{ "message": "Email re-subscribed successfully", "email": "user@example.com" }

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