canonical: https://jentic.com/apis/esendex.com

# Esendex APIs

Esendex is a business messaging provider whose APIs let you send and receive SMS, dispatch rich-content messages and surveys, schedule message batches, read conversation threads, and subscribe to delivery and inbound webhooks. Jentic publishes and maintains the OpenAPI specifications for both the full Esendex API (17 endpoints) and the narrower Esendex Messaging API (6 endpoints), keeping them validated and ready for AI agents to call. The two specs share the same base host and account model, so an agent can pick the broad surface when it needs surveys, rich content, or webhooks, or the lightweight messaging spec when it only needs core send-and-read SMS.

## For AI agents

Across the Esendex APIs an agent can dispatch one or many SMS in a single call, read the inbox and conversation threads, delete processed inbound messages, schedule and cancel message batches, send rich content and surveys, and subscribe to delivery and inbound webhooks. It can also estimate message cost and check per-message delivery status before and after sending.

## Scope

Use for: Business SMS on Esendex: sending and reading text messages, rich content, surveys, scheduled batches, conversation threads, and delivery and inbound webhooks

Not supported:
- email delivery
- push notifications
- voice calls
- video messaging
- phone number provisioning

## APIs

| API | Category | Endpoints | Description |
| --- | --- | --- | --- |
| Esendex API | communications | 17 | Send SMS, voice, rich content, and surveys, read inbox messages, manage scheduled batches, and subscribe to delivery webhooks via Esendex. |
| Esendex Messaging API | communications | 6 | Send SMS messages, list delivery headers, and read or delete inbound messages from the Esendex inbox. |

## Which API to use

| Need | API | Why |
| --- | --- | --- |
| Send and receive core SMS with delivery status and inbox reads | messaging-api | The six-endpoint Messaging API covers send, message headers, inbox read and delete, and account listing with a smaller surface to review and integrate. |
| Surveys, rich content, scheduled batches, conversation threads, or webhooks | esendex | The full 17-endpoint Esendex API adds rich-content sends, surveys with reports, batch scheduling, conversation history by phone number, cost estimation, and account-scoped webhook subscriptions. |
| Two-way messaging with a conversation thread view | esendex | Only the full Esendex API exposes GET /conversation/{phonenumber}/messages for a chronological thread across both directions; the Messaging API reads the inbox but not threaded conversations. |

## Cross-API use cases

### Start on the messaging surface, grow into the full API

A team can ship transactional SMS and inbox handling on the six-endpoint Messaging API, then add surveys, rich content, scheduled batches, and webhooks from the full Esendex API using the same account and credentials when requirements expand. An agent can route simple sends through the smaller spec and reach for the broader one only when a richer operation is needed.

Example prompt: Call POST /messagedispatcher on the Messaging API for a transactional send, then use POST /surveys/{id}/send on the Esendex API when the same workflow needs a follow-up survey.

### Right-size the SMS surface for a security review

Security-sensitive deployments can wire the minimal Messaging API for core send-and-read, while a separate workflow uses the full Esendex API for campaigns that need scheduled batches or webhook subscriptions. Choosing per workflow keeps the reviewed operation set small where it matters and broad only where the extra capability is required.

Example prompt: Use GET /inbox/messages and DELETE /inbox/messages/{messageId} on the Messaging API to consume replies, and POST /accounts/{accountReference}/subscriptions on the Esendex API to register a webhook for inbound events.

## Why Jentic

- **Setup:** Wiring Esendex by hand means supporting HTTP Basic credentials plus, for the full API, an Authorization API key, and building retries against api.esendex.com. Through Jentic you install once, add either Esendex API from the Jentic directory, store the credentials once, and your agent calls both from the same account.
- **Permission scoping:** Both Esendex specs put the message body and recipient in the request body rather than the URL, so you scope the agent to the operations it needs, such as POST /messagedispatcher or GET /inbox/messages. Your own rules decide the allowed set, so a survey send or an inbox delete is only reachable if you include it.
- **Credential handling:** Your Esendex email, API password, and Authorization API key are stored once, encrypted, by your own Jentic One instance and injected at execution time. They never enter the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'send an sms' or 'read the message inbox', and Jentic returns the matching Esendex operation with its input schema, so the agent calls the right endpoint without choosing between the two specs or the auth flavours.

## Related vendors

- **Twilio** — Programmable SMS, voice, and messaging APIs; a common alternative for two-way and transactional SMS.
- **Vonage** — Messaging and voice APIs including SMS and verification, overlapping with Esendex business messaging.
- **MessageBird** — Omnichannel SMS and conversation APIs used for notifications and two-way customer messaging.
- **ClickSend** — Business SMS, MMS, and messaging APIs positioned for notifications and campaigns like Esendex.

## FAQ

### What is the difference between the Esendex API and the Esendex Messaging API?

The Messaging API has six endpoints for core SMS: send, list and fetch message headers, read and delete inbound messages, and list accounts. The full Esendex API has seventeen endpoints and adds rich content, surveys with reports, scheduled batches, conversation threads by phone number, cost estimation, and account-scoped webhook subscriptions. Pick the Messaging API when you only need send-and-read SMS and the full API when you need the richer surface.

### Do the two Esendex APIs share the same account and credentials?

Yes. Both call the same Esendex account over the same base host and authenticate with HTTP Basic using your account email and API password. The full Esendex API also accepts an apiKey Authorization header for its rich-content and survey routes, but a single Esendex login covers both specs.

### Can I move from the Messaging API to the full Esendex API later?

Yes. Because both specs use the same account and the same POST /messagedispatcher send flow, you can start on the smaller Messaging API and add operations from the full Esendex API such as surveys, batches, or webhooks without changing vendor or re-authenticating.

### Which Esendex API should an agent use for two-way conversations?

For a threaded conversation view use the full Esendex API, which exposes GET /conversation/{phonenumber}/messages for the chronological history across both directions. The Messaging API can read and clear the inbox but does not return threaded conversations.

### What can an agent do across the Esendex APIs?

An agent can send one or many SMS in a single call, estimate message cost, track delivery status, read the inbox and conversation threads, delete processed inbound messages, schedule and cancel batches, send rich content and surveys with reports, and subscribe to delivery and inbound webhooks scoped per account.

### Are these Esendex specs official?

Esendex publishes developer documentation but not downloadable OpenAPI specifications. Jentic generates and maintains both specs, validates them against the live API, and keeps them up to date so agents and developers can call Esendex through structured tooling.