Esendex Messaging API

Name: Esendex Messaging API API
Brand: Esendex Messaging API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentCommunicationsSms Messagingbasic6 EndpointsREST

For Agents

Send SMS messages, list delivery headers, and read or delete inbound messages from the Esendex inbox. Authenticate with HTTP Basic.

Connect the Esendex Messaging API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Esendex Messaging 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.

Install Jentic One Beta (Self-Hosted)

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

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 Esendex Messaging API API.

Dispatch one or many SMS messages in a single call to /messagedispatcher

List message headers with delivery status for previously sent messages

Get a specific message header by its message ID

Read inbound messages received on your Esendex numbers

GET STARTED

Start building with Esendex Messaging API API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI document for Esendex Messaging API, keeping it validated and agent-ready.

Jentic publishes the only available OpenAPI specification for the Esendex Messaging API, keeping it validated and agent-ready. This narrower Esendex spec focuses on the core SMS send-and-read flow with six endpoints: dispatch outbound messages, list message headers with delivery status, fetch and delete inbound messages from the inbox, and list account references. It is the right choice when an integration only needs the messaging primitives and doesn't use rich content, surveys, or webhook subscriptions. Authentication is HTTP Basic with the Esendex account email and API password.

Use Cases

Patterns agents use Esendex Messaging API API for, with concrete tasks.

★ Transactional SMS for Notifications and OTPs

Product teams sending order confirmations, shipping updates, and one-time passcodes need a minimal SMS API surface. The Messaging API's POST /messagedispatcher plus GET /messageheaders/{messageId} flow covers send-and-confirm without the surface area of the larger Esendex spec, keeping integrations simple and the failure modes obvious.

Call POST /messagedispatcher with the recipient and OTP body, then poll GET /messageheaders/{messageId} until status is delivered.

Inbound SMS Processing for Reply-Driven Workflows

Workflows where customers reply YES, STOP, or short codes to an inbound number need an inbox read-and-clear pattern. The /inbox/messages and DELETE /inbox/messages/{messageId} endpoints let an agent consume new messages, parse the body, and clear the inbox so the same item is not processed twice.

Call GET /inbox/messages, process each item's body, then DELETE /inbox/messages/{messageId} for each consumed message.

Lightweight SMS Integration for Embedded Apps

Embedded or back-office apps that only need to send notifications and confirm delivery benefit from a smaller dependency surface. The six-endpoint Messaging API is enough for outbound and inbound flows without the complexity of the full Esendex spec, reducing review effort for security-sensitive deployments.

Call POST /messagedispatcher with one recipient and a notification body, then GET /messageheaders for the latest delivery status.

AI Agent Notifier via Jentic

An AI workflow agent can be wired through Jentic to send notification SMS without a custom integration. The agent searches by intent, loads the POST /messagedispatcher schema, and executes with HTTP Basic credentials scoped from the vault — useful for scheduled-task agents that text on completion or failure.

Use Jentic search('send a notification sms'), load the POST /messagedispatcher operation, and execute it with the recipient and body.

Key Endpoints

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

METHOD

PATH

DESCRIPTION

POST

/messagedispatcher

Send one or many SMS messages

GET

/messageheaders

List message headers

GET

/messageheaders/{messageId}

Get a specific message header by ID

GET

/inbox/messages

Get inbound messages

DELETE

/inbox/messages/{messageId}

Delete an inbound message

GET

/accounts

List accounts available to the user

POST

/messagedispatcher

Send one or many SMS messages

GET

/messageheaders

List message headers

GET

/messageheaders/{messageId}

Get a specific message header by ID

GET

/inbox/messages

Get inbound messages

DELETE

/inbox/messages/{messageId}

Delete an inbound message

Why though Jentic?

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

Credential isolation

Your Esendex email and API password are stored encrypted in the Jentic vault (MAXsystem) and combined into the HTTP Basic header at execution time. Raw credentials never enter the agent's context or appear in logs.

Intent-based discovery

Agents search by intent (for example 'send a notification sms' or 'read sms inbox') and Jentic returns the matching Messaging API operation plus its parameter schema, so the agent picks the right endpoint without choosing between the two Esendex specs.

Time to first call

Direct integration: half a day to wire Basic auth, batch dispatch, and inbox polling. Through Jentic: under 30 minutes — search, load, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Esendex API

Full-surface Esendex API — same vendor, broader scope (17 endpoints including surveys and rich content)

Pick the larger Esendex API when an agent needs surveys, rich content, scheduled batches, or webhook subscriptions.

Complementary

ePayTools Orchestra API

Payment orchestration — pair with SMS for receipts and 3DS step-up codes

Use when an agent confirms a payment by SMS or sends an out-of-band SCA code after a charge.

Complementary

Escrow.com API

Escrow payments — pair with SMS to notify buyers and sellers of escrow state changes

Pick when an escrow workflow needs SMS notifications on funding, shipment, and acceptance.

FAQs

Specific to using Esendex Messaging API API through Jentic.

Why is there no official OpenAPI spec for the Esendex Messaging API?

Esendex publishes developer documentation but not a downloadable OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call the Esendex Messaging API 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 Esendex Messaging API use?

The Messaging API uses HTTP Basic authentication with your Esendex account email and API password. Through Jentic the credentials are stored encrypted in the MAXsystem vault and injected at execution time so raw secrets never enter the agent's context.

Can I send an SMS with the Esendex Messaging API?

Yes. POST /messagedispatcher accepts one or many message objects (recipient, body, account reference) and returns batch metadata, which you can resolve to per-message status with GET /messageheaders/{messageId}.

What are the rate limits for the Esendex Messaging API?

Esendex governs throughput per plan but does not encode the limits in the spec. Submit large sends in a single /messagedispatcher batch rather than many parallel calls and respect 429 backoff.

How do I read inbound messages through Jentic?

Search 'read esendex inbox messages'. Jentic returns the GET /inbox/messages operation, you load its schema, and execute. Basic auth is injected from the vault.

How is this API different from the larger Esendex API?

The Messaging API has only six endpoints — send, read, delete inbound, list accounts. The larger Esendex API adds rich content, surveys, scheduled batches, conversation threads, and webhook subscriptions. Pick this one when you only need core SMS messaging.