Elastic Email API

Name: Elastic Email API API
Brand: Elastic Email API
Availability: InStock

✓ Official Vendor SpecCommunicationsEmail DeliveryapiKey15 EndpointsREST

For Agents

Send transactional or bulk emails, manage campaigns, contacts, and lists, and pull delivery statistics from Elastic Email.

Quickstart

Get started with Elastic Email API in minutes using your preferred integration method.

# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
  "jentic": {
    "url": "https://api.jentic.com/mcp",
    "auth": "oauth"
  }
}

# Then ask your agent:
"send a transactional email with Elastic Email"

# → Jentic returns the GET /events tool with parameter schema, agent executes.

Capabilities

What an agent can do with Elastic Email API API.

Send a single transactional email or a bulk send across many recipients

Create, load, update, and delete email campaigns by name

Add contacts, list contacts, and remove contacts by email address

Create lists and load existing lists in the Elastic Email account

GET STARTED

Start building with Elastic Email API API

Explore with Jentic

View OpenAPI Document

Use for: I need to send a transactional email through Elastic Email, Send a bulk email to a list of recipients, Create a new email campaign, Add a contact to my Elastic Email account

Not supported: Does not handle SMS, voice, push notifications, or webhook event ingestion — use for sending transactional and marketing email plus managing campaigns, contacts, lists, statistics, and templates only.

Elastic Email is a transactional and marketing email delivery service, and the v4 API exposes 15 endpoints covering single and bulk email send, campaign creation and management, contact and list management, statistics, and template retrieval. Authentication is a per-account API key passed in the X-ElasticEmail-ApiKey header, so server-side jobs can send transactional mail or run a marketing campaign with a single header on each request.

Use Cases

Patterns agents use Elastic Email API API for, with concrete tasks.

★ Transactional email delivery from a SaaS app

A SaaS application sends password resets, receipts, and invitations through Elastic Email. POST /emails handles individual sends, while POST /emails/transactional supports bulk transactional jobs. With a single API key, the integration is straightforward enough to wire in during a single sprint and reliable for production traffic.

POST /emails with the recipient, subject, and HTML body, then check the delivery status via GET /statistics.

Marketing campaign automation

A marketing team manages email campaigns from a custom admin tool. POST /campaigns creates a campaign, PUT /campaigns/{name} updates it, and GET /campaigns lists the existing ones. Combined with /lists for audience segments and /templates for content reuse, the Elastic Email API supports a self-serve campaign workflow without leaving the admin tool.

POST /campaigns to create a campaign, then PUT /campaigns/{name} to update its template before send.

Contact-list synchronisation from a CRM

A CRM-driven team needs Elastic Email contacts to mirror their CRM segments so newsletters target the right audience. A scheduled job uses GET /contacts and POST /contacts to add and verify contacts, and GET /lists plus POST /lists to keep audience definitions in sync. DELETE /contacts/{email} handles unsubscribes coming back from the CRM.

Diff the CRM segment against GET /contacts results, then POST /contacts for new entries and DELETE /contacts/{email} for removed entries.

Email-sending agent through Jentic

An agent platform exposes 'send an email' as a tool. Through Jentic, the agent searches by intent, receives the Elastic Email POST /emails operation, and executes it with the API key Jentic injects at runtime. The agent never sees the raw key and does not need to choose between 15 endpoints by hand.

Search Jentic for 'send a transactional email with Elastic Email', load the POST /emails schema, and execute with the recipient and content captured by the agent.

Key Endpoints

15 endpoints — elastic email is a transactional and marketing email delivery service, and the v4 api exposes 15 endpoints covering single and bulk email send, campaign creation and management, contact and list management, statistics, and template retrieval.

METHOD

PATH

DESCRIPTION

POST

/emails

Send an email

POST

/emails/transactional

Send a bulk transactional email

POST

/campaigns

Create a campaign

PUT

/campaigns/{name}

Update a campaign

GET

/contacts

List contacts

POST

/contacts

Add a contact

GET

/statistics

Load delivery statistics

GET

/templates

List templates

POST

/emails

Send an email

POST

/emails/transactional

Send a bulk transactional email

POST

/campaigns

Create a campaign

PUT

/campaigns/{name}

Update a campaign

GET

/contacts

List contacts

POST

/contacts

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Elastic Email API keys are stored encrypted in the Jentic vault (MAXsystem). Jentic injects the X-ElasticEmail-ApiKey header at execution time, so the raw key never enters the agent's context — the agent only ever has scoped execution access.

Intent-based discovery

Agents search Jentic by intent — 'send a transactional email', 'create an email campaign', 'add a contact to my list' — and Jentic returns the matching Elastic Email operation along with its input schema.

Time to first call

Direct integration: 1-2 days for a single-API-key client and basic error handling. Through Jentic: under 30 minutes — search, load schema, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

SendGrid Mail Send API

SendGrid offers a deeper email-sending API plus dedicated subusers, IP warmup, and link-branding endpoints.

Choose SendGrid when the workload needs subusers, IP warmup, or link branding; choose Elastic Email for a tighter, lower-cost transactional and campaign API.

Alternative

Brevo API

Brevo (Sendinblue) provides email plus SMS and marketing automation in one API.

Pick Brevo when the workflow needs email plus SMS or marketing automation in a single platform; pick Elastic Email for focused email delivery.

Complementary

Twilio API

Twilio handles SMS, voice, and WhatsApp alongside Elastic Email's transactional email channel.

Pair with Elastic Email when the application needs multi-channel messaging — email through Elastic Email and SMS or voice through Twilio.

FAQs

Specific to using Elastic Email API API through Jentic.

What authentication does the Elastic Email API use?

Elastic Email uses an API key passed in the X-ElasticEmail-ApiKey header on every request. Jentic stores the key encrypted in its vault and injects the header at execution time so the agent never sees the raw secret.

Can I send transactional and bulk emails through the API?

Yes. POST /emails sends a single email and POST /emails/transactional sends a bulk transactional payload. Both endpoints accept HTML and plain-text bodies plus per-recipient merge fields.

How do I manage campaigns through the API?

POST /campaigns creates a campaign, GET /campaigns lists them, GET /campaigns/{name} loads a single campaign, PUT /campaigns/{name} updates it, and DELETE /campaigns/{name} removes it. Campaigns are addressed by name in this spec.

What are the rate limits for the Elastic Email API?

Rate limits are not declared in the OpenAPI spec and depend on the Elastic Email plan and reputation tier. Use bulk endpoints for batches rather than sending one /emails request per recipient, and back off on 429 responses.

How do I send an email through Jentic?

Install the SDK with pip install jentic, search Jentic for 'send a transactional email with Elastic Email', load the POST /emails schema, and execute with the recipient, subject, and body. Jentic injects the X-ElasticEmail-ApiKey header so the agent only handles scoped execution.

Can I read delivery statistics with this API?

Yes. GET /statistics returns delivery statistics for the account; combine it with the campaigns and contacts endpoints to attribute deliverability back to specific sends.