Clickatell Platform API

Name: Clickatell Platform API API
Brand: Clickatell Platform API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentCommunicationsSms MessagingapiKey2 EndpointsREST

For Agents

Send SMS or WhatsApp messages and query delivery status through Clickatell's unified messaging platform.

Quickstart

Get started with Clickatell Platform 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 an SMS or WhatsApp message"

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

Capabilities

What an agent can do with Clickatell Platform API API.

Send a single SMS or WhatsApp message to a recipient phone number

Send the same message to multiple recipients in a single request

Query the delivery status of a previously sent message by message ID

Choose between SMS and WhatsApp channels on the same API call

GET STARTED

Start building with Clickatell Platform API API

Explore with Jentic

View OpenAPI Document

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

Jentic publishes the only available OpenAPI specification for Clickatell Platform API, keeping it validated and agent-ready. Clickatell's Platform API (One API) sends SMS and WhatsApp messages and queries the delivery status of those messages from a single unified surface. Authentication uses an API key passed in the Authorization header. The minimal endpoint set keeps integration simple while still covering the two operations that drive most messaging workflows: send and check status.

Use Cases

Patterns agents use Clickatell Platform API API for, with concrete tasks.

★ Transactional SMS Notifications

Send transactional SMS messages such as order confirmations, shipping updates, or appointment reminders through Clickatell's Platform API. The send endpoint accepts the recipient number, message body, and channel selection, then returns a message ID that can be used to verify delivery later. This pattern fits inside webhook handlers, scheduled jobs, or AI agent flows.

Call POST /v1/message with the recipient number and the order confirmation message body, then store the returned message ID against the order record.

WhatsApp Customer Messaging

Send WhatsApp messages through the same unified endpoint by selecting the WhatsApp channel on the request. This avoids running two separate integrations for SMS and WhatsApp and produces consistent message records and IDs across both channels. Useful for customer support handoffs, marketing reactivations, and channels-of-record where WhatsApp is preferred.

Call POST /v1/message with the WhatsApp channel selected and the customer's phone number to deliver the support message via WhatsApp instead of SMS.

Delivery Status Verification

Query the delivery status of a previously sent message using its message ID to confirm successful delivery, retry on failure, or attribute campaign performance. The status endpoint returns the current state of the message and is safe to poll on a backoff schedule. Useful for audit logs, compliance evidence, and retry-on-failure flows.

Call GET /v1/message/{messageId} with the stored message ID and trigger a retry workflow if the response indicates failure.

AI Agent Notification Workflow

Allow an AI agent to dispatch transactional notifications and verify their delivery without storing API keys in its own context. Through Jentic the agent searches for the send-message intent, executes the operation, and polls status — Clickatell's API key stays in the Jentic vault throughout.

Search Jentic for 'send SMS or WhatsApp message', execute POST /v1/message with the recipient and body, then poll GET /v1/message/{messageId} until status is delivered.

Key Endpoints

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

METHOD

PATH

DESCRIPTION

POST

/v1/message

Send an SMS or WhatsApp message

GET

/v1/message/{messageId}

Query the delivery status of a message

POST

/v1/message

Send an SMS or WhatsApp message

GET

/v1/message/{messageId}

Query the delivery status of a message

Why though Jentic?

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

Credential isolation

Clickatell API keys are stored encrypted in the Jentic vault. Agents send messages via Jentic's scoped access — the Authorization header value never enters the agent's prompt or context.

Intent-based discovery

Agents search Jentic for intents like 'send an SMS notification' or 'check message delivery status' and receive the matching Clickatell operation with its input schema, ready to execute.

Time to first call

Direct Clickatell integration: half a day to wire auth, send, and status polling. Through Jentic: under 15 minutes — search, load schema, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Twilio API

Programmable SMS, voice, and WhatsApp with global reach.

Choose Twilio when you need broader channel coverage including voice and programmable conferencing.

Alternative

MessageBird API

Multichannel messaging across SMS, WhatsApp, and voice.

Pick MessageBird when you also need RCS or richer omnichannel orchestration features.

Alternative

Plivo API

Developer-focused SMS and voice with low per-message pricing.

Use Plivo when cost-per-message is the primary driver.

Alternative

Sinch API

Carrier-grade SMS, MMS, and conversation APIs.

Use Sinch for very high-volume international SMS with direct carrier connectivity.

FAQs

Specific to using Clickatell Platform API API through Jentic.

Why is there no official OpenAPI spec for Clickatell Platform API?

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

Clickatell uses API key authentication. The key is sent in the Authorization header as a bearer-style value. When called via Jentic the key is stored encrypted in the Jentic vault and is never exposed to the agent's prompt context.

Can I send WhatsApp messages with the Clickatell Platform API?

Yes. POST /v1/message accepts a channel selection so the same endpoint can deliver an SMS or a WhatsApp message. This means a single integration covers both channels and produces consistent message IDs for status lookups.

How do I confirm a message was delivered?

Call GET /v1/message/{messageId} with the message ID returned by the send call. The response indicates the current delivery state, so you can poll until the message reaches a terminal state and trigger retry or notification logic accordingly.

What are the rate limits for the Clickatell Platform API?

The OpenAPI spec does not declare rate limits explicitly. Throughput is governed by your Clickatell account plan and the destination carriers. For high volumes, batch recipients within a single send request rather than firing many sequential calls.

How do I send a message through Jentic?

Search Jentic for 'send an SMS or WhatsApp message'. Jentic returns the POST /v1/message operation with its input schema. Run pip install jentic, then await client.search, await client.load, await client.execute to send the message and capture the returned message ID.