CommPeak SMS Streams API

Name: CommPeak SMS Streams API API
Brand: CommPeak SMS Streams API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentCommunicationsSms MessagingapiKey2 EndpointsREST

For Agents

Send single or batched SMS messages and check delivery status on CommPeak SMS Streams with one API key.

Connect the CommPeak SMS Streams API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the CommPeak SMS Streams 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.

Install Jentic One Beta (Self-Hosted)

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 | sh

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 instance

Jentic 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 CommPeak SMS Streams API API.

Send a single SMS message via POST /simple_send

Send a batch of SMS messages in one POST /simple_send call

Check delivery status for one or more message ids via POST /messages_status

Use a header-based API key for simple service-to-service auth

GET STARTED

Start building with CommPeak SMS Streams API API

Explore with Jentic

View OpenAPI Document

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

Jentic publishes the only available OpenAPI specification for CommPeak SMS Streams API, keeping it validated and agent-ready. The SMS Streams service is CommPeak's lightweight SMS-only surface, separate from the broader CommPeak dialler API. It exposes two endpoints: send one or more SMS messages in a single call, and check delivery status for previously sent messages. Intended for developers and QA teams that need a thin send-and-check loop without the dialler, billing, or HLR complexity of the main API.

Use Cases

Patterns agents use CommPeak SMS Streams API API for, with concrete tasks.

★ Lightweight OTP Sender

When a backend service needs to send a one-time password and confirm delivery, POST /simple_send with the destination and OTP body, then poll POST /messages_status with the returned message id. The two-endpoint surface keeps the integration small for OTP services that don't need the full CommPeak dialler.

POST to /simple_send with destination +447700900123 and body 'Your code is 482911', then POST /messages_status with the returned id

Bulk Notification Send with Status Reconciliation

Marketing or operational notifications sent in batches can be dispatched in a single POST /simple_send call carrying many messages. Capture each returned id and reconcile delivery via POST /messages_status to identify failures. The thin surface keeps batch sends fast and predictable.

POST a list of 100 messages to /simple_send, capture the ids, then POST those ids to /messages_status and return the count of failed deliveries

QA Smoke Test for SMS Pipelines

QA engineers wiring up an SMS-driven flow can use SMS Streams as the test sender. POST /simple_send fires a known-text message and POST /messages_status confirms it landed, all behind one header key. Useful in CI pipelines that exercise customer SMS journeys before promoting builds.

POST a test message to /simple_send and assert that /messages_status returns delivered within 60 seconds

AI Agent SMS Helper via Jentic

An AI agent connected to Jentic can answer 'send a reminder to this number and let me know if it lands' by calling /simple_send and /messages_status in sequence. Jentic stores the Authorization header key in the MAXsystem vault so the agent never sees the raw key.

Use Jentic to search 'send an sms via commpeak sms streams', load /simple_send, and execute with destination and body

Key Endpoints

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

METHOD

PATH

DESCRIPTION

POST

/simple_send

Send one or many SMS messages

POST

/messages_status

Check delivery status for message ids

POST

/simple_send

Send one or many SMS messages

POST

/messages_status

Check delivery status for message ids

Why though Jentic?

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

Credential isolation

The CommPeak SMS Streams Authorization header key is stored encrypted in the Jentic vault (MAXsystem). Agents call operations via Jentic and the raw key never appears in the agent's context window or logs.

Intent-based discovery

Agents search Jentic by intent (e.g., 'send an sms via commpeak sms streams') and Jentic returns the matching operation with its full input schema, so the agent calls the right endpoint without browsing CommPeak docs.

Time to first call

Direct SMS Streams integration: an hour or two to wire up two endpoints. Through Jentic: under 15 minutes — search, load, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Complementary

CommPeak API

The full CommPeak API covers dialler, PBX, billing, and HLR alongside SMS.

Use the main CommPeak API when you need dialler campaigns, billing data, or HLR lookups; SMS Streams is the focused send-and-status surface.

Alternative

Twilio Messaging API

Twilio Messaging is the dominant SMS API with global coverage and richer status webhooks.

Choose Twilio when global coverage and webhook-driven status updates matter; choose SMS Streams for a thin polling-based send-and-check loop.

Alternative

Plivo API

Plivo offers a similarly competitive SMS API with broad country coverage.

Choose Plivo for SIP-plus-SMS bundles; choose CommPeak SMS Streams for the simplest possible SMS-only integration.

FAQs

Specific to using CommPeak SMS Streams API API through Jentic.

Why is there no official OpenAPI spec for CommPeak SMS Streams API?

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

SMS Streams uses an API key passed in the Authorization header. The key is created in the CommPeak portal at my.commpeak.com under SMS Streams. Through Jentic, the key is stored encrypted in the MAXsystem vault and never enters the agent's context.

Can I send a batch of SMS messages in one request?

Yes. POST /simple_send accepts a list of messages in a single body, returning an id for each one. This is the recommended approach for marketing or notification batches over the per-message round trip.

How do I check delivery status for a sent SMS?

POST /messages_status with one or more message ids returned from /simple_send. The response contains the per-id delivery state, suitable for reconciling failures and triggering retries.

What are the rate limits for CommPeak SMS Streams?

CommPeak does not document a public rate limit for SMS Streams. In practice batched /simple_send calls scale better than tight per-message loops; expect 429 responses at extreme volume and back off.

How do I send an SMS through Jentic?

Search Jentic for 'send an sms via commpeak sms streams', load the schema for POST /simple_send, and execute with destination and body. The Jentic Python SDK pattern is await client.search(...), await client.load(...), await client.execute(...).