8x8 Connect SMS API
★ Only Publicly Available OpenAPI DocumentCommunicationsSms MessagingapiKey3 EndpointsREST
For Agents
Send single or bulk SMS messages worldwide and check delivery status using an API key. Supports GSM 7-bit and Unicode encoding plus delivery callbacks.
Use for: I need to send a verification SMS to a customer, Send a bulk SMS to a list of opted-in recipients, Check the delivery status of message UMID abc123, Send a Unicode SMS containing emoji
Not supported: Does not handle voice calls, MMS, or WhatsApp messaging — use for outbound SMS sending and delivery status only.
Jentic publishes the only available OpenAPI specification for 8x8 Connect SMS API, keeping it validated and agent-ready. The 8x8 Connect SMS API is a CPaaS interface for sending one-off and bulk SMS worldwide and tracking delivery for each message. It supports GSM 7-bit and Unicode encodings, several sender ID types (alphanumeric, short code, long code), and delivery status callbacks. The surface is small (three endpoints) and focused: one for single sends, one for batch sends, and one for status lookup by message UMID.
Install Jentic One Beta
Connect the 8x8 Connect SMS API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the 8x8 Connect SMS API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | 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.
Capabilities
What an agent can do with 8x8 Connect SMS API.
Send a single SMS to a destination MSISDN with a chosen sender ID
Send a bulk SMS batch to many recipients in one request
Look up the delivery status of a sent message by its UMID
Handle Unicode content (emoji, non-Latin scripts) via UCS-2 encoding
Receive delivery receipts via the configured callback URL
Use Cases
Patterns agents use 8x8 Connect SMS API for, with concrete tasks.
★ Transactional SMS Notifications
Operations teams use SMS to confirm orders, deliver one-time passcodes, and alert users about account events. The 8x8 Connect SMS API exposes POST /{subAccountId}/messages for single sends with a configurable sender ID and encoding, plus GET /{subAccountId}/messages/{umid} to check the result. Pair the two for a reliable send-and-confirm pattern that completes in under a second per message.
Send a single SMS to +447700900123 with body 'Your code is 482910' and then poll the status endpoint until it reports DELIVERED
Bulk Marketing or Alert Campaigns
Marketing and alerting workloads need to fan a message out to thousands of recipients with a single call. POST /{subAccountId}/batch accepts a list of destinations with the shared body, sender, and encoding, so the campaign runs as one job rather than thousands of point requests. Combine with delivery callbacks to reconcile per-recipient outcomes.
Send a batch SMS to 1,000 opted-in numbers with body 'Sale ends Friday — visit example.com' from sender ID SHOP
Delivery Reconciliation
Compliance and analytics workflows rely on accurate delivery state. GET /{subAccountId}/messages/{umid} returns the current status (delivered, failed, expired) along with the failure reason where applicable. Agents can use this to retry only on transient failures and surface permanent failures to the user.
Look up message UMID abc123 and return whether the SMS was delivered or the failure reason
Agent-Driven SMS Sending via Jentic
AI agents handle SMS as a tool call, not a custom integration. Through Jentic, an agent searches by intent, loads the schema for POST /{subAccountId}/messages, and executes the send with the API key held in the Jentic vault. The same flow covers batch sends and status checks, so an agent can run end-to-end SMS workflows without ever seeing the raw key.
Search Jentic for 'send an SMS', load the 8x8 schema, and execute the call with the customer's number and message body
Key Endpoints
3 endpoints — jentic publishes the only available openapi specification for 8x8 connect sms api, keeping it validated and agent-ready.
METHOD
PATH
DESCRIPTION
POST
/{subAccountId}/messages
Send a single SMS
POST
/{subAccountId}/batch
Send bulk SMS messages
GET
/{subAccountId}/messages/{umid}
Get SMS delivery status
POST
/{subAccountId}/messages
Send a single SMS
POST
/{subAccountId}/batch
Send bulk SMS messages
GET
/{subAccountId}/messages/{umid}
Get SMS delivery status
Why Jentic?
Three things that make agents converge on Jentic-routed access.
Credential isolation
8x8 API keys are stored encrypted in the Jentic vault. Agents call operations by ID and Jentic injects the apiKey header at execution time, so the raw key never enters the agent's context.
Intent-based discovery
Agents search by intent (e.g., 'send an SMS') and Jentic returns POST /{subAccountId}/messages with its input schema, so the agent can call the right endpoint without browsing the 8x8 docs.
Time to first call
Direct integration: 0.5-1 day to wire up auth, build the request, and add delivery-status polling. Through Jentic: minutes — search, load schema, execute.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using 8x8 Connect SMS API through Jentic.
Why is there no official OpenAPI spec for 8x8 Connect SMS API?
8x8 does not publish an OpenAPI specification for the Connect SMS endpoints. Jentic generates and maintains this spec so that AI agents and developers can call 8x8 Connect 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 8x8 Connect SMS API use?
The API uses an API key passed in the request headers (apiKey scheme). Through Jentic, the key is stored encrypted in the Jentic vault and added to the request at execution time, so the agent never sees the raw key in its context.
Can I send bulk SMS with the 8x8 Connect SMS API?
Yes. POST /{subAccountId}/batch accepts a list of destinations with a shared body, sender ID, and encoding, so a single request fans out to many recipients. Pair it with the delivery callback URL on your sub-account to reconcile per-recipient outcomes.
How do I check whether an SMS was delivered through Jentic?
Search Jentic for 'check SMS delivery status' to load GET /{subAccountId}/messages/{umid}, then execute the call with the UMID returned by your send. The response contains the current delivery state and any failure reason for retry logic.
What are the rate limits for the 8x8 Connect SMS API?
The OpenAPI spec does not document hard rate limits. 8x8's documented best practice is to respect per-route carrier throughput and use the batch endpoint for any send larger than a few hundred messages. Confirm sub-account limits in the 8x8 Connect portal before high-volume campaigns.
Does 8x8 Connect SMS support Unicode and emoji?
Yes. Set the encoding field on the message to UCS-2 (Unicode) when sending non-Latin scripts or emoji; use GSM7bit otherwise. The encoding choice affects per-segment character counts and pricing, which 8x8 calculates from the body.
GET STARTED