Exotel API

Name: Exotel API API
Brand: Exotel API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentCommunicationsSms Messagingbasic4 EndpointsREST

For Agents

Send single and bulk SMS through Exotel, look up SMS message status, and fetch the details of an Exotel voice call by its CallSid.

Quickstart

Get started with Exotel API in minutes using your preferred integration method.

# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
  "jentic": {
    "url": "https://api.jentic.com/mcp",
    "auth": "oauth"
  }
}

# Then ask your agent:
"send sms via exotel"

# → Jentic returns the GET /events tool with parameter schema, agent executes.

Capabilities

What an agent can do with Exotel API API.

Send a single SMS to a destination number from an Exotel virtual number

Send a bulk SMS campaign with per-recipient dynamic message content

Retrieve the delivery status and metadata of a specific SMS by SmsSid

Fetch the call details, duration, and status of a voice call by CallSid

Use account-scoped paths so multi-tenant agents can target the right Exotel account

GET STARTED

Start building with Exotel API API

Explore with Jentic

View OpenAPI Document

Use for: Send an SMS notification to a customer's mobile number via Exotel, Send a bulk SMS campaign with personalised content to a list of recipients, Check the delivery status of an SMS I sent earlier, Get the call duration and status for a specific Exotel call

Not supported: Does not handle outbound voice campaigns, IVR flow design, email, or push notifications — use for sending SMS, retrieving SMS status, and fetching voice call details only.

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

Jentic publishes the only available OpenAPI specification for Exotel API, keeping it validated and agent-ready. Exotel is a cloud communications platform widely used in India and South-East Asia for cloud telephony, voice calls, and SMS. This subset covers core SMS send and call-status operations: sending single and bulk SMS, retrieving SMS message details, and fetching call details by CallSid. Authentication is HTTP Basic using your Exotel API key and token.

Use Cases

Patterns agents use Exotel API API for, with concrete tasks.

★ Transactional SMS Notifications

Use POST /Sms/send to dispatch transactional SMS such as OTPs, order confirmations, or appointment reminders to Indian and South-East Asian numbers from an Exotel virtual number. Status can be confirmed with GET /SMS/Messages/{SmsSid}. Suitable for fintech, logistics, and healthcare flows where Exotel's regional regulatory compliance and DLT registration matter.

Call POST /Sms/send with To=+919876543210, From=<virtual_number>, and Body='Your OTP is 123456', then poll GET /SMS/Messages/{SmsSid} until Status is delivered.

Bulk SMS Campaigns with Dynamic Content

POST /Sms/bulksend accepts a list of recipients with per-recipient dynamic content, letting a marketing or operations agent send a campaign in a single API call. This is more efficient than looping POST /Sms/send and matches Exotel's billing model for bulk sends.

Call POST /Sms/bulksend with a list of {To, Body} pairs derived from a customer segment and capture the returned per-recipient SmsSids.

Call Outcome Reconciliation

After an Exotel voice call completes, an agent can call GET /Calls/{CallSid} to retrieve duration, status, recording URL, and from/to numbers. This is used to reconcile call outcomes into a CRM, score sales calls, or trigger downstream workflows when a customer was not reached.

Call GET /Calls/{CallSid} for a recently completed call, parse Duration and Status, and write both into the linked CRM contact.

AI Notification Agent via Jentic

An AI agent that sends customer notifications loads Exotel's send and lookup operations through Jentic. The agent searches by intent ("send an sms via exotel"), loads the operation schema, and executes with vault-held basic-auth credentials so the API key and token never enter agent context.

Through Jentic, search 'send sms via exotel', load the POST /Sms/send operation, and execute it with the recipient's number and message body.

Key Endpoints

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

METHOD

PATH

DESCRIPTION

POST

/Sms/send

Send a single SMS

POST

/Sms/bulksend

Send a bulk SMS with dynamic content per recipient

GET

/SMS/Messages/{SmsSid}

Get details of an SMS by SmsSid

GET

/Calls/{CallSid}

Get details of a call by CallSid

POST

/Sms/send

Send a single SMS

POST

/Sms/bulksend

Send a bulk SMS with dynamic content per recipient

GET

/SMS/Messages/{SmsSid}

Get details of an SMS by SmsSid

GET

/Calls/{CallSid}

Get details of a call by CallSid

Why though Jentic?

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

Credential isolation

Exotel API key and token are stored encrypted in the Jentic vault and injected as HTTP Basic auth at execution time. Raw credentials never enter the agent's prompt, memory, or logs.

Intent-based discovery

Agents search Jentic by intent (e.g., 'send an sms via exotel' or 'get call details') and receive the matching operation with its path and body schema, including the account_sid path parameter.

Time to first call

Direct Exotel integration: 1-2 days for basic auth, account_sid templating, and bulk send shape handling. Through Jentic: under 30 minutes — search, load, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Twilio API

Twilio is a global SMS and voice provider with broader country coverage than Exotel

Pick Twilio for global SMS or voice; pick Exotel when DLT-registered routing or local support in India is required.

Alternative

Plivo API

Plivo offers similar SMS and voice capabilities with global routing

Choose Plivo for international SMS at a lower cost; choose Exotel for India-first cloud telephony with local virtual numbers.

Complementary

MessageBird SMS API

MessageBird SMS adds Europe-leaning SMS coverage alongside Exotel's India-first reach

Use MessageBird when European SMS coverage matters; use Exotel for India-region SMS and voice.

FAQs

Specific to using Exotel API API through Jentic.

Why is there no official OpenAPI spec for Exotel API?

Exotel does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Exotel 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 Exotel API use?

The Exotel API uses HTTP Basic authentication with your account's API key as the username and API token as the password, both available from the Exotel dashboard. Through Jentic these credentials live in the encrypted vault and are injected per call so they never appear in agent prompts or logs.

How do I send a bulk SMS with different content per recipient?

Use POST /Sms/bulksend and supply a list of recipients each with their own message body. Exotel returns a per-recipient SmsSid array so you can correlate delivery status. This is preferred over looping POST /Sms/send for campaigns.

How do I check whether an SMS was delivered?

Call GET /SMS/Messages/{SmsSid} with the SmsSid returned at send time. The response includes Status (queued, sending, sent, delivered, failed) and any error code. Poll until Status is terminal or rely on Exotel status callbacks if you have those configured.

How do I send a transactional SMS through Jentic?

Run pip install jentic, then search 'send sms via exotel', load the POST /Sms/send operation, and execute it with To, From (your Exotel virtual number), and Body. Jentic injects basic-auth credentials at execution time.

What region does this API serve best?

Exotel is primarily a cloud communications provider for India and South-East Asia, with DLT-registered SMS routing for Indian numbers. For global SMS coverage compare against Twilio or Plivo.