Captivated Messaging API

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

★ Only Publicly Available OpenAPI DocumentCommunicationsSms Messagingbearer5 EndpointsREST

For Agents

Send single or bulk SMS messages, retrieve delivery status, track bulk send jobs, and validate phone numbers via the Captivated A2P platform. Mirrors the captivated.works spec under an alternate slug.

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 to a recipient and retrieve its delivery status by messageId

Submit a bulk send job containing many recipients and poll the resulting jobId

Retrieve per-recipient status from a bulk send job's progress endpoint

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. Captivated is an A2P messaging platform focused on SMS, and this API exposes endpoints for single sends, bulk send jobs, message status retrieval, bulk job result tracking, and phone number validation. It is the alternate-slug variant of the Captivated platform spec, mirroring the same operations against the same production base URL. Customer engagement teams use it to integrate SMS into existing workflow tools without building against vendor SDKs directly.

Use Cases

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

★ Single Transactional SMS

Workflow tools send order confirmations, OTP codes, and delivery alerts via POST /api/command/v1/messages. Latency matters here, so each call goes one-recipient-at-a-time and polls GET /api/command/v1/messages/{messageId} for delivery confirmation. Volume per call is low but frequency is high across the day.

POST /api/command/v1/messages with the recipient phone number and the message body, then poll GET /api/command/v1/messages/{messageId} to confirm delivery.

Bulk Campaign Send

Marketing campaigns submit a list of recipients to POST /api/command/v1/messages/bulk_create, which queues the send and returns a jobId. The tool polls GET /api/command/v1/jobs/{jobId} for progress and per-recipient outcomes, then writes results back to the CRM.

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

Pre-Send Phone Validation

Before charging customers for sends to bad numbers, GET /api/command/v1/phone_number_lookups/{phoneNumber} validates each number's format and reachability. The result either passes the number through to a send queue or quarantines it for manual review.

GET /api/command/v1/phone_number_lookups/+15551234567 and only enqueue numbers that the lookup marks as reachable.

AI Agent SMS Workflows

An agent that handles ticket 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 message — 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

POST

/api/command/v1/messages/bulk_create

Submit a bulk SMS job

GET

/api/command/v1/messages/{messageId}

Get delivery status for a message

GET

/api/command/v1/jobs/{jobId}

Track a bulk send job

GET

/api/command/v1/phone_number_lookups/{phoneNumber}

Validate a phone number

POST

/api/command/v1/messages

Send a single SMS

POST

/api/command/v1/messages/bulk_create

Submit a bulk SMS job

GET

/api/command/v1/messages/{messageId}

Get delivery status for a message

GET

/api/command/v1/jobs/{jobId}

Track a bulk send job

GET

/api/command/v1/phone_number_lookups/{phoneNumber}

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 on each request. Agents never see the raw token in their prompt context.

Intent-based discovery

Agents search Jentic by intent (e.g., 'send a Captivated SMS' or 'submit a Captivated bulk job') and Jentic returns the matching 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. Tokens are user-created, non-expiring, and revocable from the user profile. Through Jentic the token is stored encrypted in the vault and injected into the Authorization header at execution time.

Can I send a bulk SMS with the Captivated API?

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

How do I check a phone number's deliverability through Jentic?

Search Jentic for 'validate a phone number with Captivated', load the lookupPhoneNumber operation, and execute GET /api/command/v1/phone_number_lookups/{phoneNumber}. The response indicates whether the number is reachable.

What are the rate limits for the Captivated Messaging API?

Captivated does not enumerate 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.

What is the difference between this slug and captivated.works/main?

Both slugs point to the same Captivated platform. captivated.works/main is the canonical vendor-domain slug; captivated/main is an alternate slug some pipelines pin to. New integrations should prefer captivated.works/main.

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