Elastic Email API + MCP (2026): v4 REST, 13 SDKs, first-party MCP

Elastic Email exposes a JSON REST API at https://api.elasticemail.com/v4, backed by 13 official SDKs (Python, Node, C#, PHP, Java, Ruby, Go, Rust, Perl, Bash, plus two TypeScript flavours) refreshed in May 2026. The company also shipped its own first-party MCP server at mcp.elasticemail.com in October 2025, the same year SendGrid and Mailgun still relied on community wrappers, making it one of the few ESPs where campaigns, contacts, templates and Send-HTTP are all reachable from Claude or Cursor with a single API key.

At a glance

MCP integration in 2026

Elastic Email is one of a small group of ESPs that ship a first-party Model Context Protocol server. That matters because it removes the DIY wrapper step: any MCP-capable client. Claude Desktop, ChatGPT, Cursor, Copilot, Gemini CLI, can drive campaigns, lists, contacts, templates and transactional sends by pointing at a single hosted URL and supplying an API key.

Available MCP servers

As of August 2026 the Elastic Email MCP surface splits into one official hosted server, the vendor’s own landing/setup page, one community directory entry and a marketplace bridge via Zapier. All entries below are reachable from any MCP-capable IDE or chat client.

Elastic Email API essentials

The v4 surface is built around eight logical resource families: sending (/emails, /emails/transactional, /emails/mergefile), audience (/contacts, /lists, /segments), content (/templates, /campaigns, /files), deliverability (/domains, /suppressions, /verifications), telemetry (/statistics, /events, /webhook), reseller (/subaccounts), inbound (/inboundroute) and security (/security/apikeys). Compared with Brevo‘s broader marketing surface, Elastic Email keeps the API tight and transactional-first while still shipping full campaign management for Marketing-plan customers.

Authentication methods

HTTP header (recommended)

All v4 REST calls should carry the X-ElasticEmail-ApiKey HTTP header with the API key value. The key is created inside the Elastic Email dashboard under Settings › Security › API Keys, and every key can be scoped to a subset of resources (Campaigns, Contacts, Templates, Send HTTP, etc.). Rotating a key is a delete + create operation, there is no in-place rotation endpoint.

API key query parameter

Legacy code and some v2 examples pass the key as ?apikey=YOUR_KEY. It still works on v4, but it will end up in HTTP access logs, browser history, proxy caches and any client-side network trace. Prefer the header; keep the query-parameter form for one-off curl smoke tests only.

MCP token

The MCP server at mcp.elasticemail.com uses a different header name-X-Auth-Token-but the value is still an Elastic Email API key. The key must be scoped to Account, Templates, Campaigns, Contacts, Files, Send HTTP and view rights on Access Tokens. Missing any of these silently degrades the tool list an LLM sees.

Rate limits

The workaround for the 20-concurrent ceiling is the same as with any provider that throttles per source IP: cap your worker pool at 20, add jitter between requests, and shard high-volume traffic across multiple egress IPs (NAT gateways, worker regions). If you are migrating from SendPulse or MailerSend where per-hour caps are the visible constraint, the mental model shifts: with Elastic Email the concurrency limit is the binding one, not raw throughput.

Official SDKs

Elastic Email ships 13 official SDKs across every mainstream language plus Rust, Perl and Bash. All repositories were last refreshed in May 2026, which is closer to active than SparkPost‘s aging client set and comparable to Mailgun‘s cadence.

Notable community SDKs

Because the official SDK matrix is broad, third-party wrappers are rare and rarely needed. Elixir, Clojure and Erlang shops typically use a plain HTTP client (Finch, clj-http, hackney) against v4 rather than a community library. The one community pattern worth calling out is Sendy and MailWizz configurations that use Elastic Email as an SMTP relay, both projects document how to plug smtp.elasticemail.com in without ever touching the SDK matrix, which suits self-hosted marketing users who only need the SMTP surface.

Endpoints reference

The v4 surface exposes 18 resources at https://api.elasticemail.com/v4. The full OpenAPI spec is published at the official REST reference. The table below summarises the 18 top-level resources; each supports the standard subset of HTTP verbs listed.

Code examples

Python, send transactional email

import ElasticEmail
from ElasticEmail.api import emails_api
from ElasticEmail.model.email_content import EmailContent
from ElasticEmail.model.body_part import BodyPart
from ElasticEmail.model.body_content_type import BodyContentType
from ElasticEmail.model.transactional_recipient import TransactionalRecipient
from ElasticEmail.model.email_transactional_message_data import EmailTransactionalMessageData

configuration = ElasticEmail.Configuration()
configuration.api_key['apikey'] = 'YOUR_API_KEY'

with ElasticEmail.ApiClient(configuration) as api_client:
    api = emails_api.EmailsApi(api_client)
    payload = EmailTransactionalMessageData(
        recipients=TransactionalRecipient(to=['user@example.com']),
        content=EmailContent(
            body=[BodyPart(
                content_type=BodyContentType('HTML'),
                content='<strong>Hello from Elastic Email</strong>',
                charset='utf-8',
            )],
            _from='sender@yourdomain.com',
            subject='Transactional test',
        ),
    )
    api.emails_transactional_post(payload)

Node.js, send bulk email

const ElasticEmail = require('@elasticemail/elasticemail-client');

const defaultClient = ElasticEmail.ApiClient.instance;
defaultClient.authentications['apikey'].apiKey = 'YOUR_API_KEY';

const api = new ElasticEmail.EmailsApi();

const email = ElasticEmail.EmailMessageData.constructFromObject({
  Recipients: [ new ElasticEmail.EmailRecipient('user@example.com') ],
  Content: {
    Body: [ ElasticEmail.BodyPart.constructFromObject({
      ContentType: 'HTML',
      Content: '<strong>Hello from Elastic Email</strong>'
    }) ],
    Subject: 'Transactional test',
    From: 'sender@yourdomain.com'
  }
});

api.emailsPost(email, (err, data) => {
  if (err) return console.error(err);
  console.log('Sent:', data);
});

Common gotchas

Deprecations and changelog

• December 10, 2025-Canva integration launched. Design in Canva and export directly to Elastic Email with a shared media library.
• October 20, 2025–mcp.elasticemail.com went live. First-party MCP server exposing campaigns, contacts, lists, segments, templates, files and Send HTTP to Claude, ChatGPT, Cursor, Copilot and Gemini CLI.
• August 15, 2025-AI Template Designer released. Natural-language prompts generate templates that are then reusable through /templates.
• July 15, 2025-Paid Newsletters launched with Stripe payment processing built in.
• April 30, 2025-Checkouts feature launched, enabling sale of digital products directly through myelasticemail.com product pages.
• April 15, 2025-Creator Suite launched (signup forms, link-in-bio, email designer, automation) inside the v4 workspace.

Track future changes on the official Elastic Email blog and the REST API reference. The v2 API remains online for legacy customers but is not receiving new features, treat it as maintenance mode.

Frequently asked questions