Captivated Works Captivated Messaging API

Name: Captivated Messaging API
Brand: Captivated Messaging API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentCommunicationsSms Messagingbearer5 EndpointsREST

For Agents

Send SMS or MMS messages individually or in bulk, schedule delivery, attach files, and track bulk send jobs. Includes a phone number lookup endpoint for pre-send validation.

Install Jentic One Beta

Connect the Captivated Messaging API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Captivated Messaging 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://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: 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 Captivated Messaging API.

Send a single SMS or MMS to a recipient with optional attachments

Submit a bulk message job to deliver to many recipients in a single request

Schedule a message for future delivery and retrieve its status by message id

GET STARTED

Start building with Captivated Messaging API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI specification for Captivated Messaging API, keeping it validated and agent-ready. The Captivated Messaging API sends individual and bulk SMS or MMS messages with support for scheduled delivery, image and file attachments, and asynchronous job tracking for large sends. It also provides phone number lookups so senders can validate destination numbers before dispatch. Customer engagement teams use it to drive marketing blasts, transactional alerts, and conversational replies from existing CRM and ticketing tools.

Use Cases

Patterns agents use Captivated Messaging API for, with concrete tasks.

★ Transactional SMS Alerts

Operational systems send order updates, appointment reminders, and verification codes via POST /api/command/v1/messages. The endpoint accepts a single recipient with optional attachments and returns a message id that can be polled at GET /api/command/v1/messages/{message_id} to confirm delivery. Volume is moderate and latency-sensitive.

POST /api/command/v1/messages with the recipient phone number and the alert text, then poll GET /api/command/v1/messages/{message_id} to confirm delivery.

Bulk Marketing Send

Marketing campaigns blast a promotion to a segmented contact list. POST /api/command/v1/messages/bulk_create accepts the list of recipients in a single call and returns a job id. The team polls GET /api/command/v1/jobs/{job_id} for progress and per-recipient status, treating the call as fire-and-forget once submission succeeds.

POST /api/command/v1/messages/bulk_create with the array of recipients and the message body, then poll GET /api/command/v1/jobs/{job_id} until completion.

Phone Number Validation Pipeline

Before adding a number to a contact list or sending a costly MMS, GET /api/command/v1/phone_number_lookups/{phone_number} validates the number's format and reachability. The lookup result feeds a CRM data quality rule and prevents wasted sends to unreachable numbers.

GET /api/command/v1/phone_number_lookups/+15551234567 and write the lookup result against the contact record in the CRM.

AI Agent Outbound Messaging

An agent that triages support follow-ups uses Captivated via Jentic to send a personalised SMS once a ticket closes. It searches for the send-message operation, loads the schema, and submits the SMS — credentials stay encrypted in the Jentic vault throughout.

Search Jentic for 'send a Captivated SMS', load the createMessage schema, and execute POST /api/command/v1/messages with the recipient and body.

Key Endpoints

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

METHOD

PATH

DESCRIPTION

POST

/api/command/v1/messages

Send a single SMS or MMS

POST

/api/command/v1/messages/bulk_create

Submit a bulk message job

GET

/api/command/v1/messages/{message_id}

Get delivery status of a message

GET

/api/command/v1/jobs/{job_id}

Track a bulk send job

GET

/api/command/v1/phone_number_lookups/{phone_number}

Validate a phone number

POST

/api/command/v1/messages

Send a single SMS or MMS

POST

/api/command/v1/messages/bulk_create

Submit a bulk message job

GET

/api/command/v1/messages/{message_id}

Get delivery status of a message

GET

/api/command/v1/jobs/{job_id}

Track a bulk send job

GET

/api/command/v1/phone_number_lookups/{phone_number}

Validate a phone number

Why Jentic?

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

Credential isolation

The Captivated bearer token is stored encrypted in the Jentic vault and injected into the Authorization header at execution time. Agents never receive the raw token.

Intent-based discovery

Agents search Jentic by intent (e.g., 'send an SMS' or 'submit a bulk SMS job') and Jentic returns the matching Captivated operation with its input schema, so the agent picks the right one of the 5 endpoints without browsing docs.

Time to first call

Direct Captivated integration: a few hours for bearer auth, message scheduling, and bulk job polling. Through Jentic: under 30 minutes — search, load schema, execute.

FAQs

Specific to using Captivated Messaging API through Jentic.

Why is there no official OpenAPI spec for Captivated Messaging API?

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

Captivated uses bearer token authentication, with the token obtained from the user profile under Password and Credentials. Through Jentic the bearer token is stored encrypted in the vault and never appears in the agent's prompt context.

Can I send a bulk SMS to thousands of recipients with the Captivated API?

Yes. POST /api/command/v1/messages/bulk_create accepts an array of recipients in one request and returns a job id. Poll GET /api/command/v1/jobs/{job_id} for the per-recipient delivery status.

How do I send a scheduled SMS through Jentic?

Search Jentic for 'send a Captivated SMS', load the createMessage operation, and execute POST /api/command/v1/messages with the recipient, body, and a scheduled_at timestamp in the request payload.

What are the rate limits for the Captivated Messaging API?

Captivated does not publish rate limits in the OpenAPI spec. Bulk sends are queued asynchronously, so prefer bulk_create over many single calls and back off on 429 responses.

Can I attach an image to a Captivated message?

Yes. The createMessage payload supports attachments, sending it as MMS instead of plain SMS. Confirm the recipient carrier supports MMS via GET /api/command/v1/phone_number_lookups/{phone_number} before sending costly MMS at scale.

Captivated Works Captivated Messaging API

Connect the Captivated Messaging API to your agent

Capabilities

Start building with Captivated Messaging API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs