
A cold email API lets your code — or an automation tool — control outreach without clicking through dashboards. But "cold email API" means two different things, and most articles only cover one. Sequencer APIs (Instantly, Smartlead and similar) control campaigns, leads and replies. Infrastructure APIs control the layer underneath: domains, DNS, mailboxes, workspaces and the export of inboxes into those sequencers. This guide explains how the two layers fit together, what a complete API-driven setup looks like, how LiteMail's API connects email infrastructure to outreach platforms, and the deliverability guardrails that must stay in place when everything is automated.
What Is a Cold Email API? The Short Answer
A cold email API is an HTTP interface for automating cold outreach. An infrastructure API buys or connects domains, configures DNS, creates Google Workspace or Microsoft 365 mailboxes and exports them to a sending platform. A sequencer API then adds leads, runs campaigns and returns replies. Connected together, they let agencies and SaaS teams provision and launch outreach programmatically.
Layer | What the API controls | Examples |
|---|---|---|
Infrastructure | Domains, DNS records, mailboxes, workspaces, export to platforms, placement tests | LiteMail API (docs.litemail.ai) |
Sending / sequencing | Campaigns, leads, sequences, schedules, replies, webhooks | Instantly, Smartlead and other sequencers' APIs |
Data | Prospect search, enrichment, verification | Data and verification providers |
CRM | Deals, contacts, activity sync | HubSpot, Salesforce, Pipedrive |
🚩 Transactional email APIs are not cold email APIs
Services built for receipts and notifications generally require opt-in recipients and are the wrong tool for cold outreach. Cold email should go out from real Google Workspace or Microsoft 365 mailboxes connected to a sequencer.
How Infrastructure Connects to Outreach Platforms
Provision domains. Register new secondary domains or connect existing ones.
Configure DNS. SPF, DKIM, DMARC, MX and forwarding records.
Create mailboxes. Google Workspace or Microsoft 365 inboxes on those domains, grouped by client or brand workspace.
Export to the sequencer. Connect inboxes to Instantly, Smartlead, Lemlist or similar — ideally via OAuth rather than app passwords.
Launch campaigns. The sequencer API adds leads and starts sequences with per-inbox limits.
Monitor. Webhooks, placement tests, warm-up analytics and mailbox status feed dashboards and alerts.
OAuth connections are generally more stable than SMTP app passwords; our Smartlead setup guide, Google Workspace + Smartlead integration and Microsoft 365 + Smartlead integration walk through the connection step.
The LiteMail API: What It Covers
LiteMail's API documentation at docs.litemail.ai describes a REST API with base URL https://api.litemail.app/v1. Requests are authenticated with a bearer token in the Authorization header, and an x-workspace-key header targets a specific workspace (otherwise the user's primary workspace is used). The documentation lists a soft limit of 5 requests per second per user with a burst allowance; exceeding it returns 429 Too Many Requests, and retries with exponential backoff are recommended. LiteMail's site lists API access on its Pro and Scale plans.
Resource group | Documented endpoints (examples) |
|---|---|
Domains | Retrieve domains, purchase/register, connect domains, check DNS records, add DMARC, name servers, forwarding, catch-all |
Mailboxes | Retrieve, assign to domain, update, remove at renewal, warm-up analytics |
Workspaces | List, create, update workspaces |
Exports | Export mailboxes, add third-party account details, connect inboxes (export to platform), export history |
DNS | Get, create, update, delete DNS records |
Placement | List and create placement tests |
Dashboard | Overview and mailbox status counts |
Webhooks | List, register and delete webhook endpoints |
Billing & subscriptions | Wallet balance, invoices, subscriptions |
Cloudflare | Credentials, zones and domain connection |
Endpoint names are taken from the public documentation index; check each endpoint page for request and response details before building.
What Teams Automate with a Cold Email API
🏢Client onboarding for agencies
Create a workspace, register domains and mailboxes and export them to the client's sequencer workspace in one script — see LiteMail for agencies and client onboarding guide.
🧩SaaS products with built-in outreach
Provision infrastructure per customer behind your own UI; see LiteMail for SaaS teams.
📈Capacity scaling
Add mailboxes when campaign volume grows instead of raising per-inbox limits (why).
🩺Health monitoring
Pull mailbox status counts, warm-up analytics and placement tests into dashboards.
🔁Domain rotation
Rest domains with weak metrics and bring in replacements, such as pre-warmed domains.
🧾DNS audits
Check DNS records across every domain to catch broken SPF/DKIM before it causes Outlook 550 5.7.515 bounces.
Deliverability Guardrails for API-Driven Outreach
Automation makes mistakes faster too. Build these rules into code, not just policy:
Hard per-inbox caps in the sequencer, far below provider limits (Gmail limits, Microsoft 365 limits).
Gradual ramps for new mailboxes (warm-up guide) or start with pre-warmed inboxes.
Verification before upload — never push unverified leads (list cleaning).
Suppression sync across workspaces so opt-outs are honoured everywhere.
Automatic pausing when bounces or complaints spike (email throttling).
Backoff on 429s from any API, including LiteMail's 5 requests/second soft limit.
Secrets management for tokens and mailbox credentials.
Choosing a Cold Email API Stack
Question | Why it matters |
|---|---|
Does the infrastructure API create real Google Workspace / Microsoft 365 mailboxes? | Official mailboxes connect to any sequencer and are portable |
Does it automate DNS authentication? | SPF, DKIM and DMARC are mandatory for bulk senders |
Can it export to your sequencer? | Saves manual OAuth work at scale |
Does it support workspaces per client or brand? | Isolation protects reputation |
Are there webhooks and health data? | Needed for automated monitoring |
What are the rate limits? | Determines how you batch and retry |
Comparing infrastructure providers? See LiteMail vs Zapmail, LiteMail vs Infraforge, LiteMail vs Instantly and Mailforge alternative. Platform-independence matters if you might switch sequencers later; see inbox options across platforms.
Example: Automating a New Client Launch with a Cold Email API
Illustrative workflow. An agency wants every new client live within a day. With a cold email API on the infrastructure side and a sequencer API on the sending side, the flow looks like this:
Step | API layer | What happens |
|---|---|---|
1 | Infrastructure | Create a workspace for the client |
2 | Infrastructure | Register or connect 3–6 secondary domains; check DNS records |
3 | Infrastructure | Assign mailboxes to domains (Google Workspace and/or Microsoft 365) |
4 | Infrastructure | Export/connect inboxes to the client's sequencer workspace |
5 | Sequencer | Create campaign, set per-inbox daily caps and send windows |
6 | Data + Sequencer | Upload only verified leads; sync suppression list |
7 | Both | Register webhooks; schedule placement tests and status checks |
Endpoint names will differ by provider — check each platform's documentation. Agencies building this should also read white-label cold email services, the LiteMail agency plan and agency infrastructure. The affiliate program is an option if you refer clients rather than resell. Before launch, make sure the client's domains will avoid Outlook 550 5.7.515 and that lists are cleaned (guide).
Build on the LiteMail API
LiteMail | Infrastructure API for outreach
API on Pro and Scale plans
Domains, DNS, mailboxes, workspaces and exports — programmatically
LiteMail provisions official Google Workspace and Microsoft 365 inboxes with automated SPF, DKIM and DMARC on dedicated US and EU IPs, and its API exposes domains, DNS, mailboxes, workspaces, exports, placement tests and webhooks. Pro ($297/month, 100 inboxes) and Scale ($849/month, 300 inboxes) plans include API access per LiteMail's pricing table; use the pricing calculator to size it.
Strengths | Keep in mind |
|
|
Read the API Docs → Automate infrastructure provisioning and connect it straight to your outreach platform. See Pre-Warmed Plans →
Frequently Asked Questions
What is a cold email API?
It is an API that automates cold outreach. Infrastructure APIs manage domains, DNS and mailboxes; sequencer APIs manage campaigns, leads and replies.
Can I send cold email through a transactional email API?
Generally no. Transactional services are built for opt-in and system emails. Cold outreach should use real Google Workspace or Microsoft 365 mailboxes through a sequencer.
Does LiteMail have an API?
Yes. LiteMail's documentation at docs.litemail.ai covers domains, DNS, mailboxes, workspaces, exports, placement tests, webhooks and billing. LiteMail lists API access on Pro and Scale plans.
How does LiteMail's API authenticate?
With a bearer token in the Authorization header; an x-workspace-key header targets a specific workspace.
What are LiteMail's API rate limits?
The documentation lists a soft limit of 5 requests per second per user with a short burst allowance; exceeding it returns 429, and exponential backoff is recommended.
Can the API connect inboxes to Instantly or Smartlead?
LiteMail's API documentation includes export endpoints, including connecting inboxes to platforms. LiteMail also supports bulk OAuth export from the dashboard.
Should I connect inboxes via OAuth or SMTP?
OAuth is generally more stable and secure than app passwords. See our Smartlead configuration guide.
How do I keep API-driven cold email deliverable?
Enforce per-inbox caps, gradual ramps, list verification, suppression sync and automatic pausing on bounce or complaint spikes.
Connect Infrastructure to Outreach — Programmatically
LiteMail's API manages domains, DNS, Google Workspace and Microsoft 365 mailboxes, workspaces and exports, on dedicated US and EU IPs.
REST API · Workspaces · Export to sequencers · Webhooks
About LiteMail — LiteMail provides fresh and pre-warmed Google Workspace and Microsoft 365 inboxes for cold email outreach, with automated SPF, DKIM and DMARC setup, dedicated US and EU IPs, separate client workspaces and one-click OAuth export to Instantly, Smartlead, Lemlist and other sending tools. View pre-warmed inbox plans →
Related reading: Cold Email Inbox Setup for Smartlead · Google Workspace + Smartlead Integration · Cold Email Agency Setup Guide · Scaling to 500 Inboxes · Cold Email Infrastructure · Bulk Email Inboxes


