CommPeak API

Name: CommPeak API API
Brand: CommPeak API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentCommunicationsVoice Telephonybearer39 EndpointsREST

For Agents

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.

Connect the CommPeak API to your agent

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

Initiate outbound calls and click-to-call sessions via GET /click2call

Manage dialler campaigns and leads via /campaigns and /leads endpoints

Send transactional SMS via POST /sms/send and check delivery status

Run synchronous or asynchronous HLR lookups via /lookup/sync and /lookup/async

GET STARTED

Start building with CommPeak API API

Explore with Jentic

View OpenAPI Document

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

Jentic publishes the only available OpenAPI specification for CommPeak API, keeping it validated and agent-ready. CommPeak provides cloud communications infrastructure: an outbound dialler, cloud PBX, SMS via TextPeak, HLR number lookup, billing data, and an SMS gateway. The unified API spans 39 endpoints across calls, campaigns, leads, users, do-not-call lists, call detail records, SMS sending, HLR lookups, and billing rates. Use it to run sales call centres, send transactional SMS, validate phone numbers, and pull rate cards for cost reporting.

Use Cases

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

★ Outbound Sales Dialler Automation

Push leads from a CRM into CommPeak via POST /leads, dispatch them to a campaign with GET /dispatch/leads, and start calls with /click2call. Pull aggregated stats from GET /calls/aggregated to track campaign performance. The dialler-leads-campaigns triangle automates the full outbound motion without manual list uploads.

POST a new lead to /leads with phone number and campaign id, then GET /dispatch/leads to confirm assignment

Transactional SMS at Scale

Send OTPs, appointment reminders, and shipping updates via POST /sms/send. Track delivery via POST /sms/status to confirm receipt. Combine with /lookup/sync to validate the destination number before sending, reducing failed deliveries and wasted spend.

POST an SMS to /sms/send with destination +447700900123 and body 'Your code is 123456'

Phone Number Validation Pipeline

Before importing a contact list into the dialler, run each number through GET /lookup/sync to confirm the network and reachability. Bad numbers can be filtered out or routed to /dnc to prevent dialler waste. The async variant /lookup/async + /lookup/result/{requestId} suits large batch validations.

GET /lookup/sync with phone parameter +14155552671 and return the network and ported status

AI Agent Voice Operations via Jentic

An AI agent connected to Jentic can answer 'what did we spend on outbound calls yesterday?' by pulling /cdrs and /billing/voice-rates. Or it can place a click-to-call when a high-priority lead replies. Jentic stores the bearer token in MAXsystem so the agent never sees the raw key.

Use Jentic to search 'send an sms through commpeak', load POST /sms/send, and execute with destination and body

Key Endpoints

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

METHOD

PATH

DESCRIPTION

POST

/sms/send

Send an SMS message

GET

/click2call

Initiate a click-to-call

GET

/calls

List calls

POST

/leads

Create a lead

GET

/lookup/sync

Synchronous HLR lookup

POST

/dnc

Add a number to the do-not-call list

GET

/cdrs

List call detail records

GET

/billing/voice-rates

Get voice rate card

POST

/sms/send

Send an SMS message

GET

/click2call

Initiate a click-to-call

GET

/calls

List calls

POST

/leads

Create a lead

GET

/lookup/sync

Synchronous HLR lookup

POST

/dnc

Add a number to the do-not-call list

Why though Jentic?

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

Credential isolation

The CommPeak bearer token is stored encrypted in the Jentic vault (MAXsystem). Agents call operations via Jentic and the raw token never enters the agent's context window or logs.

Intent-based discovery

Agents search Jentic by intent (e.g., 'send an sms through commpeak') 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 CommPeak integration: 1-2 days to handle the multi-host base URL (Dialler, TextPeak, HLR, SMS gateway) and bearer auth across services. Through Jentic: under 1 hour — search, load, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Twilio Messaging API

Twilio is the dominant cloud communications platform with deeper coverage but higher complexity.

Choose Twilio for global enterprise scale and a richer ecosystem; choose CommPeak when its dialler-plus-SMS bundling and pricing fit a sales call-centre use case.

Alternative

Plivo API

Plivo offers voice and SMS APIs at competitive pricing similar to CommPeak's positioning.

Choose Plivo when SIP infrastructure and developer SDK breadth matter most; choose CommPeak when its integrated dialler is the core need.

Alternative

MessageBird SMS API

MessageBird (now Bird) covers SMS, voice, and omnichannel messaging across global networks.

Choose MessageBird for omnichannel (SMS plus WhatsApp, email, voice) at scale; choose CommPeak for outbound sales-focused workloads.

Complementary

Telnyx API

Telnyx provides SIP trunking and number management that can sit upstream of CommPeak's dialler.

Pair with Telnyx when sourcing numbers or routing calls through a separate carrier; CommPeak handles the dialler workflow.

FAQs

Specific to using CommPeak API API through Jentic.

Why is there no official OpenAPI spec for CommPeak API?

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

CommPeak uses a bearer token in the Authorization header on every request. Through Jentic the token is stored encrypted in the MAXsystem vault and never enters the agent context — the agent only sees execution results.

Can I send SMS messages with the CommPeak API?

Yes. POST /sms/send sends an SMS through the TextPeak service; POST /sms/status returns delivery status for a given message id. The base URL for SMS endpoints is https://tp-api.commpeak.com/v1.

Does the CommPeak API support phone number validation?

Yes. GET /lookup/sync runs a synchronous HLR lookup against the live mobile network; POST /lookup/async + GET /lookup/result/{requestId} handles large batch validations. The base URL for lookups is https://hlr-api.commpeak.com/v1.

What are the rate limits for the CommPeak API?

CommPeak does not publish a hard public rate limit. Practical limits depend on the customer's plan and the underlying service (dialler vs SMS vs HLR). Expect 429 responses at extreme volume and back off with retries.

How do I send an SMS through Jentic?

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