CM.com Business Messaging API

Name: CM.com Business Messaging API API
Brand: CM.com Business Messaging API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentCommunicationsSms MessagingapiKey5 EndpointsREST

For Agents

Send SMS, RCS, WhatsApp, Viber and other channel messages, validate phone numbers, and check which messaging channels a number supports.

Quickstart

Get started with CM.com Business Messaging API in minutes using your preferred integration method.

# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
  "jentic": {
    "url": "https://api.jentic.com/mcp",
    "auth": "oauth"
  }
}

# Then ask your agent:
"send an SMS via CM.com"

# → Jentic returns the GET /events tool with parameter schema, agent executes.

Capabilities

What an agent can do with CM.com Business Messaging API API.

Send SMS, RCS, WhatsApp, Viber and Apple Messages for Business through a single POST /message endpoint

Check whether a phone number supports a specific channel via GET /v1/capabilities/{phoneNumber}

Run bulk capability checks for thousands of numbers in one call to /v1/capabilities

Validate phone number formatting and reachability with GET /numbervalidation/{phoneNumber}

GET STARTED

Start building with CM.com Business Messaging API API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI document for CM.com Business Messaging API, keeping it validated and agent-ready.

Jentic publishes the only available OpenAPI specification for CM.com Business Messaging API, keeping it validated and agent-ready. The API delivers messages across SMS, RCS, WhatsApp, Viber, Apple Messages for Business, and other conversational channels through a single send endpoint that accepts a list of recipients and a channel-specific payload. It also provides number validation, HLR-based number lookup, and per-channel capability checks so callers can confirm whether a given mobile number can receive a particular message type before sending.

Use Cases

Patterns agents use CM.com Business Messaging API API for, with concrete tasks.

★ Multi-Channel Customer Notifications

Send time-sensitive notifications such as order confirmations, delivery updates, and OTP codes across SMS, WhatsApp, RCS, and Viber from a single POST /message call. The API accepts a list of recipients and a channel preference, so callers can fall back from a richer channel like RCS to SMS when a number is not reachable. Integration with the unified send endpoint typically takes under a day for SMS-only flows and two to three days when adding template-based WhatsApp.

Send an SMS to +31612345678 with body 'Your order #4521 has shipped' using POST /message and confirm the message status.

Phone Number Validation Before Outreach

Validate phone numbers in user signup and CRM imports before storing them, removing malformed entries and reducing failed-send costs. GET /numbervalidation/{phoneNumber} returns whether the number is correctly formatted and reachable, while /numberlookup/{phoneNumber} adds carrier, country, and roaming detail. Replacing in-house regex validation with this endpoint usually takes under half a day.

Call GET /numbervalidation/+447911123456 and return whether the number is valid and reachable.

Channel Capability Routing

Decide at runtime which messaging channel to use for each recipient by querying capabilities. POST /v1/capabilities accepts a list of numbers and returns per-channel reachability so a marketing or transactional flow can pick RCS where supported and fall back to SMS otherwise. This pattern reduces wasted spend on rich-message attempts that silently fall back to SMS at the operator level.

POST a list of 100 phone numbers to /v1/capabilities and return which numbers support RCS.

AI Agent Messaging Through Jentic

An AI agent uses Jentic to discover and call the CM.com send endpoint without storing the X-CM-PRODUCTTOKEN header value in its own context. The agent searches for 'send an SMS', loads the schema for POST /message, and executes with the recipient and body. Jentic injects credentials at execution time, so the same workflow works in CrewAI, LangChain, or a custom agent loop.

Use Jentic to search for 'send an SMS', load the POST /message schema, and send 'Welcome' to a single recipient.

Key Endpoints

5 endpoints — jentic publishes the only available openapi specification for cm.

METHOD

PATH

DESCRIPTION

POST

/message

Send messages on SMS, RCS, WhatsApp, Viber, and other channels

GET

/v1/capabilities/{phoneNumber}

Check channel capabilities for a single phone number

POST

/v1/capabilities

Bulk channel capability check

GET

/numbervalidation/{phoneNumber}

Validate a phone number

GET

/numberlookup/{phoneNumber}

HLR-based number lookup

POST

/message

Send messages on SMS, RCS, WhatsApp, Viber, and other channels

GET

/v1/capabilities/{phoneNumber}

Check channel capabilities for a single phone number

POST

/v1/capabilities

Bulk channel capability check

GET

/numbervalidation/{phoneNumber}

Validate a phone number

GET

/numberlookup/{phoneNumber}

HLR-based number lookup

Why though Jentic?

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

Credential isolation

The X-CM-PRODUCTTOKEN header value is stored encrypted in the Jentic vault. Agents call CM.com operations without ever receiving the raw product token — Jentic injects it at execution time and rotates it on demand.

Intent-based discovery

Agents search by intent (e.g. 'send an SMS' or 'validate a phone number') and Jentic returns the matching CM.com operation with its input schema, so the agent can construct a valid payload without reading the docs.

Time to first call

Direct CM.com integration: half a day to one day for an SMS-only flow plus extra time for WhatsApp template approval. Through Jentic: under one hour — search, load schema, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Sinch

Sinch offers a comparable multi-channel messaging stack covering SMS, MMS, WhatsApp and Viber.

Choose Sinch when the workload needs deep MMS support or a stronger Asia-Pacific delivery footprint.

Alternative

Plivo

Plivo provides SMS, voice, and WhatsApp APIs with global reach.

Choose Plivo if the task also needs programmable voice in addition to messaging.

Alternative

Telnyx

Telnyx offers SMS, MMS, voice, and number provisioning over a self-owned IP network.

Choose Telnyx when latency control or owning the underlying number routing matters.

Complementary

Twilio Messaging

Twilio Messaging covers SMS, MMS, and WhatsApp with mature US carrier coverage.

Use Twilio alongside CM.com when redundancy or US-specific shortcode support is required.

FAQs

Specific to using CM.com Business Messaging API API through Jentic.

Why is there no official OpenAPI spec for CM.com Business Messaging API?

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

The API uses an API-key scheme called productToken, sent as the X-CM-PRODUCTTOKEN header on every request. Through Jentic the product token is stored encrypted in the vault and injected at execution time, so an agent never sees the raw key in its prompt or logs.

Can I send WhatsApp and RCS messages through the CM.com API?

Yes. The single POST /message endpoint accepts a channel hint and supports SMS, RCS, WhatsApp, Viber, Apple Messages for Business, and other conversational channels. Check reachability first with GET /v1/capabilities/{phoneNumber} before attempting a richer channel.

What are the rate limits for the CM.com Business Messaging API?

The OpenAPI spec does not declare numeric rate limits. CM.com applies tenant-specific throughput based on your account tier and channel; high-volume SMS and bulk capability checks should be paginated and throttled client-side. Confirm your account limits with CM.com support before large bulk runs.

How do I validate a phone number with the CM.com API through Jentic?

Search Jentic for 'validate a phone number', load the GET /numbervalidation/{phoneNumber} schema, and execute with the E.164 number. The response indicates whether the number is correctly formatted and reachable. Install the SDK with pip install jentic and call it via the async client.

Does the CM.com API support bulk channel capability checks?

Yes. POST /v1/capabilities accepts a list of phone numbers and returns per-channel reachability for each, which is the preferred path when routing thousands of recipients across SMS, RCS and WhatsApp in a single workflow.