Jentic publishes the only available OpenAPI specification for the Esendex API, keeping it validated and agent-ready. Esendex provides SMS, voice, rich-content messaging, surveys, and webhook subscriptions for business communications. The 17 endpoints cover the full message lifecycle: dispatch via /messagedispatcher, list message headers and inbox, read conversations by phone number, manage scheduled batches, send rich content and surveys, and create webhook subscriptions per account. Authentication is dual: HTTP Basic for the historical SMS endpoints and an apiKey Authorization header for newer rich-content and survey routes.
17 endpointsJentic 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.
6 endpointsStep 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" | shStep 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" | 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.