MailLandDocs

API reference

Every endpoint you can call with an API key, generated from the MailLand OpenAPI document.

This reference lists every endpoint an integration can call with an API key. It is generated from the API's own OpenAPI document, filtered to the endpoints that accept an API key; the customer panel's own endpoints (sign-in, account, team, billing) are not part of the public API and are not listed.

Base URL and authentication

All requests go to https://api.mail.land and carry your key in the X-API-Key header:

curl https://api.mail.land/v1/transactional/send \
  -H "X-API-Key: ml_pet_..." \
  -H "Content-Type: application/json" \
  -d '{"from":{"email":"[email protected]"},"to":[{"email":"[email protected]"}],"subject":"Hello","htmlContent":"<p>Hello</p>"}'

Production sending keys start with ml_pet_ (transactional) or ml_pem_ (marketing). Sandbox keys start with ml_set_ or ml_sem_, inbound keys with ml_pi_ and validation keys with ml_pv_. See API keys.

Never send an API key as Authorization: Bearer, and never put it in code that runs in a browser.

Sections

Sending

Send, batch send, scheduled sends, email log, follow-ups.

Templates

Templates and their versions.

Domains

Sending domains and their DNS records.

Suppressions and bounces

The suppression list and bounces.

Webhooks

Webhook endpoints and deliveries.

Inbound email

Inbound domains, routes and messages.

Analytics and deliverability

Statistics and deliverability reports.

Email validation

Single and batch validation.

Marketing

Lists, subscribers, segments, campaigns, automations.

Errors and limits apply to every endpoint: see Error codes and Rate limits. The compatibility promise for /v1 is in API compatibility.

On this page

Base URL and authenticationSections