Cellcast SMS API

Name: Cellcast SMS API API
Brand: Cellcast SMS API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentCommunicationsSms MessagingapiKey23 EndpointsREST

For Agents

Send SMS messages, manage contacts and lists, and track delivery and replies through the Cellcast Australian SMS gateway. Maintain opt-out lists and read credit usage history.

Quickstart

Get started with Cellcast SMS 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 through Cellcast"

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

Capabilities

What an agent can do with Cellcast SMS API API.

Send single or bulk SMS messages to Australian mobile numbers via /sms/send

Pull SMS send history and inbound responses for delivery tracking and reply handling

Manage contacts and contact lists with create, update, and delete operations

Maintain an opt-out list to suppress contacts who have requested no further messages

GET STARTED

Start building with Cellcast SMS API API

Explore with Jentic

View OpenAPI Document

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

Jentic publishes the only available OpenAPI specification for the Cellcast SMS API, keeping it validated and agent-ready. Cellcast is an Australian SMS and MMS messaging provider used for bulk send, two-way messaging, and customer notifications. The v4 API exposes endpoints for sending SMS, reading send history and inbound responses, managing contacts and contact lists, maintaining an opt-out list, and handling credit recharge packages and transactions. Authentication is a single APPKEY header.

Use Cases

Patterns agents use Cellcast SMS API API for, with concrete tasks.

★ Bulk SMS Campaign Send with Suppression

Marketing teams send bulk campaign messages to thousands of Australian mobile numbers and need to suppress opted-out recipients before each send. An agent reads the opt-out list, removes those numbers from the contact list, and posts the campaign to /sms/send. Send history is then polled to confirm delivery counts.

GET /optout/list to fetch suppressions, then POST /sms/send with the cleaned recipient list and campaign body

Two-Way SMS Customer Service

Customer-service teams use a dedicated Cellcast number for two-way conversations with customers. An agent polls /sms/responses for inbound messages, routes them to the right human agent or chatbot, and posts replies via /sms/send. This turns a single Cellcast number into the SMS channel for a full support workflow.

Poll GET /sms/responses every minute, classify each message, and POST /sms/send with the appropriate reply

Contact List Maintenance

Customer data teams keep Cellcast contact lists in sync with the source-of-truth CRM so campaigns target the latest segments. Agents call /contact/create, /contact/update, and /list/create to mirror CRM changes, then verify with /contact/list and /list. This keeps audience segments fresh without a manual export-import.

Diff the CRM contact set against GET /contact/list and apply additions via POST /contact/create and updates via PUT /contact/update

AI Agent Integration via Jentic

An operations agent uses Jentic to send SMS notifications as one step in a larger workflow that also touches CE event data, calendaring, or finance APIs. Cellcast credentials stay in the encrypted vault while the agent triggers /sms/send through scoped execution.

Use Jentic to search 'send an SMS through Cellcast', load the schema for POST /sms/send, and execute with the recipient and body

Key Endpoints

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

METHOD

PATH

DESCRIPTION

POST

/sms/send

Send an SMS message

GET

/sms/history

View SMS send history

GET

/sms/responses

Get inbound SMS responses

POST

/contact/create

Create a contact

GET

/optout/list

View opted-out contacts

POST

/recharge/purchase

Purchase a recharge package

GET

/account/details

View account details

POST

/sms/send

Send an SMS message

GET

/sms/history

View SMS send history

GET

/sms/responses

Get inbound SMS responses

POST

/contact/create

Create a contact

GET

/optout/list

View opted-out contacts

POST

Why though Jentic?

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

Credential isolation

Cellcast APPKEYs are stored encrypted in the Jentic vault. The agent triggers /sms/send and contact endpoints through scoped execution requests; the raw APPKEY header value never enters the agent context.

Intent-based discovery

Agents search Jentic by intent (e.g., 'send a bulk SMS in Australia') and Jentic returns the Cellcast /sms/send operation along with related opt-out and contact list calls needed in the workflow.

Time to first call

Direct Cellcast integration: half a day to a day for auth, send payload shaping, and reply polling. Through Jentic: under 30 minutes — search, load schema, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

BulkSMS API

Global bulk SMS gateway with similar contact and send endpoints

Choose BulkSMS when the customer needs cross-border SMS coverage; choose Cellcast for Australia-first flows

Alternative

MessageBird SMS API

Global multi-channel messaging API including SMS, WhatsApp, and voice

Choose MessageBird when the customer needs cross-border SMS or omnichannel; choose Cellcast for Australia-only flows

Complementary

CE-Go API

Continuing education event registration data that pairs well with SMS reminders

Pair Cellcast with CE-Go to send SMS event reminders to CE registrants

FAQs

Specific to using Cellcast SMS API API through Jentic.

Why is there no official OpenAPI spec for the Cellcast SMS API?

Cellcast publishes API documentation pages but not a structured OpenAPI artifact. Jentic generates and maintains this spec so that AI agents and developers can call Cellcast SMS 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 Cellcast SMS API use?

Cellcast uses an APPKEY header — a single application key that authenticates each request. Through Jentic the APPKEY value sits in the encrypted vault and is injected at execution time, so the agent never holds it directly.

Can I send bulk SMS to Australian numbers with Cellcast?

Yes. POST /sms/send accepts a list of recipient numbers and the message body. Combine with /optout/list before each send to suppress opted-out numbers and stay compliant with Australian SPAM Act consent rules.

What are the rate limits for the Cellcast SMS API?

The OpenAPI spec does not declare a numeric rate limit. Cellcast enforces fair-use throttling at the APPKEY level and meters credits per message. Plan bulk campaigns against your credit balance and back off on 429 responses.

How do I send an SMS through Jentic?

Search Jentic for 'send an SMS through Cellcast', load the schema for POST /sms/send, and execute with the recipient number and message body. Inbound replies can be polled via GET /sms/responses in the same agent.

Is the Cellcast SMS API free?

API access is free; messages are billed per credit. Buy credits via /recharge/purchase or pre-purchased packages on cellcast.com.au — there is no per-call API charge beyond message credits.