canonical: https://jentic.com/apis/commpeak.com

# CommPeak APIs

CommPeak provides cloud communications infrastructure for outbound sales and messaging. Across its two APIs, agents can run outbound dialler campaigns, manage leads and do-not-call lists, place click-to-call sessions, send single or batched SMS messages, validate phone numbers via HLR lookup, and pull call detail records and billing rate cards. The main CommPeak API covers voice, dialler, SMS, HLR, and billing across 39 endpoints, while the SMS Streams API is a focused two-endpoint surface for sending SMS and checking delivery status.

## For AI agents

An agent can run outbound dialler campaigns, place click-to-call sessions, send single or batched SMS, validate numbers via HLR lookup, maintain do-not-call lists, and pull call detail records and billing rates across CommPeak's voice and messaging APIs.

## Scope

Use for: Outbound dialler campaigns, click-to-call voice, transactional and batched SMS, HLR number validation, and call and billing record reporting on CommPeak

Not supported:
- email delivery
- video conferencing
- in-app push notifications
- webhook delivery status
- omnichannel messaging

## APIs

| API | Category | Endpoints | Description |
| --- | --- | --- | --- |
| CommPeak API | communications | 39 | Run outbound dialler campaigns, send SMS, look up phone numbers via HLR, and pull billing rates and call records on CommPeak with one bearer token. |
| CommPeak SMS Streams API | communications | 2 | Send single or batched SMS messages and check delivery status on CommPeak SMS Streams with one API key. |

## Which API to use

| Need | API | Why |
| --- | --- | --- |
| Send a transactional SMS or OTP | sms-streams-api | SMS Streams is the thin two-endpoint send-and-status surface with no dialler or billing dependencies, best for simple transactional or batch sends. |
| Send SMS alongside voice, dialler, HLR, or billing work | commpeak-api | The main API sends SMS via TextPeak in the same token scope as calls, campaigns, lookups, and rate cards, so one integration covers a full outbound motion. |
| Reconcile SMS delivery status | sms-streams-api | messages_status returns per-id delivery state for reconciling failures without pulling the broader call and billing data of the main API. |

## Cross-API use cases

### Validate and message a lead list

Run each contact number through the main API's HLR lookup to confirm reachability, filter out invalid numbers, then dispatch the confirmed batch through SMS Streams as a single send and reconcile delivery status. This keeps validation in the full API while using the thin SMS surface for the send.

Example prompt: GET /lookup/sync for each number on the main API, then POST the reachable ones as a batch to /simple_send on SMS Streams and POST their ids to /messages_status

### Dialler campaign with SMS follow-up

Push leads into a dialler campaign and place calls through the main CommPeak API, then send an SMS follow-up through SMS Streams to numbers that did not connect. The main API handles the voice motion while SMS Streams keeps the messaging leg lightweight.

Example prompt: POST leads to /leads and start calls with /click2call on the main API, then POST an SMS to /simple_send on SMS Streams for unconnected numbers

### Cost-aware SMS reporting

Send transactional messages through SMS Streams and reconcile delivery, then pull SMS rate cards from the main API's billing endpoints to attribute spend per message batch. This separates the send path from the billing data source.

Example prompt: POST a batch to /simple_send on SMS Streams, then GET SMS rate cards from /billing on the main API to compute batch cost

## Why Jentic

- **Setup:** Wiring CommPeak by hand means learning two separate auth schemes, hitting distinct hosts for dialler, SMS, and HLR, and reconciling call and billing records yourself. Through Jentic you install Jentic One once, add either CommPeak API from the Jentic directory, store each credential once, and your agent calls both.
- **Permission scoping:** CommPeak sends target numbers, campaign details, and message bodies in request bodies, so your own rules in Jentic One decide which operations each agent may call. You can allow HLR lookups, billing reads, or SMS status checks while leaving outbound dialling and message sending out unless you add them.
- **Credential handling:** Both the main API bearer token and the SMS Streams API key are stored encrypted by your own Jentic One instance and injected only at execution time. Neither credential enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search the Jentic directory by intent such as 'send an SMS' or 'check voice call records', and Jentic returns the matching CommPeak operation with its input schema, so the agent picks the right endpoint across both APIs without browsing reference docs.

## Related vendors

- **Twilio** — Dominant cloud communications platform with broader global voice and SMS coverage and webhook-driven status.
- **Plivo** — Voice and SMS APIs at competitive pricing with SIP infrastructure, a common alternative for outbound workloads.
- **MessageBird** — Omnichannel messaging across SMS, WhatsApp, email, and voice for teams that need more than voice and SMS.
- **Telnyx** — SIP trunking and number management that can sit upstream of a dialler for sourcing numbers and routing calls.

## FAQ

### What can an AI agent do across CommPeak's APIs?

An agent can run outbound dialler campaigns, manage leads and do-not-call lists, place click-to-call sessions, send single or batched SMS, validate phone numbers with HLR lookup, and pull call detail records and billing rate cards. The main CommPeak API covers the full voice and messaging stack, while the SMS Streams API is a focused surface for sending SMS and checking delivery status.

### How are the two CommPeak APIs different?

The main CommPeak API is a broad 39-endpoint surface spanning dialler, cloud voice, SMS via TextPeak, HLR lookup, and billing. The SMS Streams API is a two-endpoint SMS-only service for sending messages and checking delivery status, meant for teams that want a thin send-and-check loop without the dialler or billing complexity.

### Which API should an agent use to send an SMS?

Use SMS Streams when the task is only sending a message or an OTP and confirming delivery, since it is smaller and simpler. Use the main CommPeak API when the SMS is part of a larger flow that also touches calls, campaigns, HLR lookups, or billing, so a single integration covers the whole motion.

### Do both CommPeak APIs share one credential?

No. The main CommPeak API authenticates with a bearer token in the Authorization header, and the SMS Streams API uses a separate API key in the Authorization header. Each is issued and managed independently, so an agent working across both needs both credentials configured.

### Are these CommPeak specs official?

CommPeak does not publish OpenAPI specifications for these APIs. Jentic generates and maintains both specs, validates them against the live APIs, and keeps them agent-ready so an agent can call them through structured tooling.

### Can CommPeak handle omnichannel messaging like WhatsApp or email?

No. CommPeak focuses on voice, SMS, and number validation. It does not cover email delivery, video conferencing, in-app push, or channels such as WhatsApp. For omnichannel needs, pair it with a dedicated messaging vendor while using CommPeak for voice and SMS.