CommPeak API

Name: CommPeak API
Brand: CommPeak API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentCommunicationsVoice Telephonybearer39 EndpointsREST

Install Jentic One Beta

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.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fcommpeak.com%2Fcommpeak-api" | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fcommpeak.com%2Fcommpeak-api" | 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.

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

GET STARTED

Start building with CommPeak API

Explore with Jentic One

View OpenAPI Document

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.

Use for: Send a transactional SMS to a customer through CommPeak, Initiate a click-to-call between an agent and a lead, Create a new lead and assign it to a dialler campaign, List today's call detail records (CDRs)

Not supported: Does not handle email delivery, video conferencing, or in-app push notifications - use for outbound voice dialling, SMS, HLR lookup, and billing data only.

Use Cases

Patterns agents use CommPeak 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 your Jentic One instance 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 Jentic?

What agents get from Jentic-routed access to this vendor.

Setup

Wiring CommPeak by hand means learning its bearer auth, wiring separate outbound voice, SMS, and HLR lookup calls, and reconciling call and billing records yourself. Through Jentic you install once, import CommPeak from the API Directory, store the token once, and your agent calls it.

Permission scoping

CommPeak sends the target number and campaign details in the request body, so limit the agent to the operations it needs, such as sending an SMS or fetching call records. You choose the operations it may call, so you can allow lookups and billing reads while leaving outbound dialling out unless you add it.

Credential isolation

Your CommPeak bearer token 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.

Intent-based discovery

Agents search Jentic 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 calls the right endpoint without browsing the reference docs.

FAQs

Specific to using CommPeak 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 with Jentic One, the self-hosted execution layer.

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 your Jentic One instance 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(...).

Can I limit what my agent is allowed to do with the CommPeak API?

Yes. Because Jentic One is self-hosted by you, your own rules decide which CommPeak operations and credentials the agent may use. You can allow read-only actions like HLR lookups on /lookup/sync, call records on /cdrs, and billing reads on /billing/voice-rates while withholding outbound dialling on /click2call and SMS sends on /sms/send unless you explicitly add them. Since CommPeak passes the target number and campaign details in the request body, scoping the agent to only the operations it needs keeps it from placing calls or texts you did not authorise.

CommPeak API

Connect the CommPeak API to your agent

Capabilities

Start building with CommPeak API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs