EmailLabs API

Name: EmailLabs API
Brand: EmailLabs API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentCommunicationsEmail Deliverybasic16 EndpointsREST

For Agents

Send transactional emails, manage templates, track events, maintain blacklists, and configure webhooks via EmailLabs. Authenticated with HTTP Basic.

Install Jentic One Beta

Connect the EmailLabs API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the EmailLabs API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with EmailLabs API.

Send transactional emails via POST /new_sendmail with attachments and templates

List and fetch named email templates for reuse across campaigns

Pull a list of sent emails and per-message details for support investigations

GET STARTED

Start building with EmailLabs API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI specification for EmailLabs API, keeping it validated and agent-ready. EmailLabs is a transactional email delivery platform with 16 endpoints covering sending, templates, tracked emails, blacklist management, sending statistics, SMTP accounts, sending domains, and webhooks. Authentication is HTTP Basic against https://api.emaillabs.net.pl/api. The send and stats endpoints are the heart of the API; the blacklist and webhooks endpoints exist to keep deliverability and event reporting in good shape.

Use Cases

Patterns agents use EmailLabs API for, with concrete tasks.

★ Transactional Email Sending

Send password resets, receipts, and notification emails through EmailLabs by calling POST /new_sendmail with the recipient, subject, body, and optional template reference. The send endpoint returns a message_id used later with GET /emails/{message_id} to confirm delivery. Suitable for production traffic of millions of transactional messages per month per account.

POST a transactional email to user@example.com using template_id=welcome with name=Alex; on response, log the message_id

Deliverability Monitoring and Blacklist Hygiene

Run a daily job that reads /events for bounces and complaints, adds the offending addresses to the blacklist via POST /blacklist, and removes addresses from the blacklist on customer request via DELETE /blacklist/{email}. Combined with /stats, this keeps sender reputation healthy and provides a clear audit trail.

Read bounce events from GET /events, then POST each bouncing address to /blacklist with reason='hard bounce'

Webhook-Driven Event Processing

Register a webhook via POST /webhooks to receive delivery, open, click, and bounce events in real time. The webhook list can be inspected with GET /webhooks and a noisy or deprecated webhook can be removed with DELETE /webhooks/{webhook_id}. This lets a downstream system (CRM, analytics, support tool) react to email events without polling.

POST a new webhook pointed at https://my.app/webhooks/emaillabs subscribing to delivery, open, and bounce events

AI Agent Integration via Jentic

Build an AI customer-support agent that drafts a personalised reply, sends it via EmailLabs using a templated layout, and looks up the resulting message_id to confirm delivery. Through Jentic, the agent searches by intent, loads the send schema, and executes without holding the HTTP Basic credentials in its prompt.

Search Jentic for 'send a transactional email', load the schema for POST /new_sendmail, and send a templated reply to the customer's email

Key Endpoints

16 endpoints — jentic publishes the only available openapi specification for emaillabs api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

POST

/new_sendmail

Send an email

GET

/sendmail_templates

List email templates

GET

/emails

List sent emails

GET

/events

List email events

GET

/stats

Get sending statistics

POST

/blacklist

Add an address to the blacklist

POST

/webhooks

Create a webhook

POST

/new_sendmail

Send an email

GET

/sendmail_templates

List email templates

GET

/emails

List sent emails

GET

/events

List email events

GET

/stats

Get sending statistics

POST

/blacklist

Add an address to the blacklist

Why Jentic?

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

Credential isolation

EmailLabs HTTP Basic credentials are stored encrypted in the Jentic vault (MAXsystem) and injected at execution time. Agents never hold the raw username or password in prompts or memory.

Intent-based discovery

Agents search by intent (e.g. 'send a transactional email' or 'add to blacklist') and Jentic returns the matching EmailLabs operation with its input schema, so the agent picks the right endpoint without parsing the upstream docs.

Time to first call

Direct integration: 4-8 hours to wire HTTP Basic, a webhook receiver, and a blacklist sync job. Through Jentic: under 30 minutes — search, load schema, execute.

FAQs

Specific to using EmailLabs API through Jentic.

Why is there no official OpenAPI spec for EmailLabs API?

EmailLabs publishes its API documentation as a marketing-and-docs site at emaillabs.io rather than as a versioned OpenAPI specification. Jentic generates and maintains this spec so AI agents and developers can call EmailLabs via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.

What authentication does the EmailLabs API use?

EmailLabs uses HTTP Basic authentication. Through Jentic, the username and password pair is stored encrypted in the vault and added to outgoing requests at execution time so the agent never sees the raw credentials.

Can I send a transactional email with EmailLabs?

Yes. POST /new_sendmail accepts the recipient, subject, body, optional template reference, and attachments, and returns a message_id you can later use with GET /emails/{message_id} to confirm delivery.

How do I receive delivery events in real time?

Register a webhook via POST /webhooks pointing at your callback URL. Webhooks deliver open, click, bounce, and other events as they happen; the GET /webhooks endpoint lists currently registered callbacks and DELETE /webhooks/{webhook_id} removes them.

How do I send a templated email through Jentic?

Run the Jentic search query 'send a transactional email', load the input schema for POST /new_sendmail, then execute with the recipient, template ID, and merge fields. Jentic injects the HTTP Basic credentials at execution time.

Where is the EmailLabs API hosted?

The API base URL is https://api.emaillabs.net.pl/api — a Polish-domain endpoint that reflects EmailLabs' EU operating base. This is relevant for teams that need an EU-hosted transactional email provider for GDPR or data-residency reasons.

EmailLabs API

Connect the EmailLabs API to your agent

Capabilities

Start building with EmailLabs API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs