Esendex Messaging API
Browse all Esendex APIs40
AI ReadinessFoundational (D-)40/100
Agent-ready OpenAPI document · curated by JenticCommunicationsSms Messagingbasic6 EndpointsREST
Know of an official OpenAPI document? Contribute it →
For Agents
Send SMS messages, list delivery headers, and read or delete inbound messages from the Esendex inbox. Authenticate with HTTP Basic.
Use for: Send an SMS to +447900900123 saying 'order confirmed', Get the delivery status of message ID 0123-4567, List the most recent inbound messages, Delete an inbound message after I have processed it
Not supported: Does not handle rich content messages, surveys, scheduled batches, or webhook subscriptions - use for core SMS send and inbox operations only.
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.
Install Jentic One Beta
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.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fesendex.com%2Fmessaging-api" | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fesendex.com%2Fmessaging-api" | sh
jentic register # connects your agent to your Jentic One instanceJentic 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.
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
Delete a specific inbound message from the inbox after processing
List the accounts available under the authenticated Esendex login
Use Cases
Patterns agents use Esendex Messaging 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
GET
/accounts
List accounts available to the user
Jentic AI Readiness Score
This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.
E
Esendex Messaging API
- Foundational (D-)40/100
100
Foundational Compliance63
Developer Experience & Jentic Compatibility47
AI-Readiness & Agent Experience94
Agent Usability10
Security100
AI DiscoverabilityPowered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.0
Show dimension breakdown
100
Foundational Compliance
Base layer of spec validity and structural soundness.
Grade: A+Signals: 4
99%
Lint Results
Aggregated quality score from linter diagnostics, weighted by severity.
100%
Resolution Completeness
Percentage of `$ref` references that resolve successfully.
100%
Specification Validity
Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).
100%
Structural Integrity
Structural correctness score based on schema issues using logarithmic dampening.
63
Developer Experience & Jentic Compatibility
Clarity, completeness, and ingestion readiness for developers and tooling.
Grade: B-Signals: 4
0%
Example Density
How richly the API is illustrated with examples.
100%
Example Validity
Percentage of examples that conform to their schemas.
50%
Response Coverage
Percentage of operations with complete response definitions (success, client error, server error).
100%
Tooling Readiness
Health of API ingestion, bundling, and resolution within Jentic pipelines.
47
AI-Readiness & Agent Experience
Semantic breadth, depth, and agent comprehension for AI systems.
Grade: DSignals: 4
38%
Description Coverage
Coverage of descriptions across API elements.
0%
Error Standardization
Coverage of RFC 9457 Problem Details for error responses.
100%
OperationId Quality
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
50%
Summary Coverage
Coverage of summaries across operations/tags/info.
94
Agent Usability
Functional utility, complexity comfort, and AI orchestration readiness.
Grade: A+Signals: 1
94%
Complexity Comfort
Agent comfort level based on API operational and structural complexity.
10
Security
Trust, risk posture, and security compliance.
Grade: FSignals: 1
10%
Authentication Strength
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
100
AI Discoverability
Findability, semantic richness, and reasoning readiness.
Grade: A+Signals: 1
100%
Descriptive Richness
Clarity and depth of descriptions across API elements.
Score it yourself
Every API in the directory is allowlisted, so you can re-score it with no key required.
npx @jentic/api-scorecard-cli score <openapi-url>Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the Esendex Messaging API by hand means combining your email and API password into an HTTP Basic header and building your own retries against api.esendex.com. Through Jentic you install once, import the Esendex Messaging API from the API Directory, store the credentials once, and your agent calls it.
Permission scoping
The Messaging API sends the message body and recipient in the request body rather than the URL, so scope the agent to the operations it needs, such as POST /messagedispatcher or GET /inbox/messages. You pick that allowed set, so a destructive operation like DELETE /inbox/messages/{messageId} is only reachable if you include it.
Credential isolation
Your Esendex email and API password are stored once, encrypted, by your own Jentic One instance and combined into the Basic header at execution time. They never enter the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'send a notification sms' or 'read the sms inbox', and Jentic returns the matching Messaging API operation with its input schema so the agent calls the right endpoint without choosing between the two Esendex specs.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using Esendex Messaging 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 with Jentic One, the self-hosted execution layer.
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 your Jentic One instance 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.
Can I limit what my agent is allowed to do with the Esendex Messaging API?
Yes. Because Jentic One is self-hosted, you decide which of the Messaging API's six operations your agent may call, so you can allow read-and-send operations like POST /messagedispatcher and GET /inbox/messages while leaving the rest off. A destructive operation such as DELETE /inbox/messages/{messageId} is only reachable if you explicitly include it in the allowed set. Your Esendex email and API password are stored encrypted by your own instance and combined into the HTTP Basic header at execution time, so raw credentials never enter the agent's context.
GET STARTED