canonical: https://jentic.com/apis/cellcast.com.au/cellcast # Cellcast SMS API 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. ## For AI 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. ## Scope Does not handle voice calls, email, or push notifications - use for SMS and MMS messaging on the Cellcast Australian gateway only. ## Capabilities - 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 - Purchase recharge packages and read transaction and credit-usage history - Read account details and update payment information for the SMS account ## Use cases ### 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. Example prompt: 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. Example prompt: 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. Example prompt: 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. Example prompt: 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 | 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 | ## Key resources - **SMS** — Send messages, view send history, and read inbound responses - **Contacts** — Create, update, list, and delete individual contacts - **Lists** — Manage contact lists used as send audiences - **Opt-out** — Maintain the opt-out list to suppress contacts before campaigns - **Account** — Read account details and create accounts - **Recharge** — View packages, manage payment info, and purchase credit - **Reports** — Read credit usage history ## Why Jentic - **Setup:** Wiring the Cellcast SMS API by hand means handling its APPKEY header, sending against the Australian gateway host, and reconciling send history, responses, and opt-outs yourself. Through Jentic you install once, import Cellcast from the API Directory, store the key once, and your agent calls it. - **Permission scoping:** Cellcast carries the message and recipient in the request body rather than a resource path, so scope your agent to the operations it needs, such as sending SMS and reading history, and leave account recharge out unless it should spend. Every operation you credit it with is one you have added to the allowed set. - **Credential handling:** Your Cellcast APPKEY is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context. - **Discovery method:** Agents search Jentic by intent such as 'send a bulk SMS in Australia' or 'list opt-outs', and Jentic returns the matching Cellcast operation with its input schema so the agent calls the right endpoint without browsing the reference docs. ## Related APIs - **BulkSMS API** — Global bulk SMS gateway with similar contact and send endpoints - **MessageBird SMS API** — Global multi-channel messaging API including SMS, WhatsApp, and voice - **CE-Go API** — Continuing education event registration data that pairs well with SMS reminders ## FAQ ### 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 with Jentic One, the self-hosted execution layer. ### 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. ### Can I limit what my agent is allowed to do with the Cellcast SMS API? Yes. Because you run Jentic One yourself, your own rules decide which Cellcast operations and credentials the agent may use, and each operation is only callable once you add it to the allowed set. For a send-and-monitor agent you can permit POST /sms/send, GET /sms/history, and GET /sms/responses while leaving account and credit operations like /recharge/purchase out, so the agent cannot spend on your account. Since Cellcast carries the recipient and message in the request body rather than the path, scoping is done at the operation level rather than by resource path.