SMS API

Name: SMS API API
Brand: SMS API
Availability: InStock

✓ Official Vendor SpecCommunicationsSms MessagingapiKey5 EndpointsREST

For Agents

Send, list, retrieve, update, and delete SMS messages across Twilio, MessageBird, Vonage, and Plivo through one unified API.

Connect the SMS API to your agent

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

Send an SMS to a phone number with body and optional sender ID via POST /sms/messages

List sent and received messages with cursor pagination through GET /sms/messages

Look up the delivery status of a specific message by ID

Update a queued message's body or scheduled-send time before it is dispatched

GET STARTED

Start building with SMS API API

Explore with Jentic

View OpenAPI Document

The Apideck SMS API is a focused unified interface for sending and managing SMS messages across providers including Twilio, MessageBird, Vonage, and Plivo. Five endpoints cover the full message lifecycle — list, create, get, update, and delete — so a SaaS product can hand SMS sending to whichever provider the customer has connected without writing per-vendor code. Authentication uses the standard Apideck Authorization header alongside x-apideck-app-id and x-apideck-consumer-id. Designed for transactional messaging, OTPs, and notifications rather than for bulk marketing campaigns.

Use Cases

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

★ Cross-Provider Transactional SMS

Send transactional SMS — verification codes, order confirmations, appointment reminders — through whichever provider the customer has connected (Twilio, MessageBird, Vonage, Plivo) without writing per-vendor code. POST /sms/messages takes a phone number and body and returns the resulting message ID; GET /sms/messages/{id} reports delivery status. Useful for SaaS products that want to delegate provider choice to their customers.

Send an SMS to '+15551234567' with body 'Your verification code is 482910' and return the message_id and initial status

OTP and Verification Flows

Build a one-time-password flow on top of the Apideck SMS API. POST /sms/messages with the OTP body, then poll GET /sms/messages/{id} or rely on the customer's connected provider's webhook to confirm delivery. The same code path works whether the customer's connection is Twilio, MessageBird, Vonage, or Plivo.

Generate a 6-digit code, POST /sms/messages with body 'Your code: <code>' to the user's phone, and return both the code and the message_id

Scheduled Reminder Cancellation

Manage queued SMS reminders. POST /sms/messages with a scheduled-send time creates a queued message; PATCH /sms/messages/{id} updates the body or time; DELETE /sms/messages/{id} cancels it before dispatch. Useful for appointment-booking products where the customer might reschedule and the reminder needs to update or be cancelled.

List queued messages for phone '+15551234567', and for each one with a scheduled_send_time before tomorrow PATCH the time to one hour later

AI Agent SMS Notification via Jentic

An AI agent fires off an SMS as part of a workflow — for example, alerting a customer that an order has shipped. Through Jentic, the agent searches 'send an sms', loads the POST /sms/messages operation, and executes it with the recipient and body. Jentic stores the Apideck Authorization, x-apideck-app-id, and x-apideck-consumer-id headers separately so the agent never holds raw credentials.

Through Jentic, search 'send an sms', load POST /sms/messages, and send a shipping confirmation SMS with the tracking link to the customer's phone number

Key Endpoints

5 endpoints — the apideck sms api is a focused unified interface for sending and managing sms messages across providers including twilio, messagebird, vonage, and plivo.

METHOD

PATH

DESCRIPTION

GET

/sms/messages

List SMS messages

POST

/sms/messages

Send an SMS message

GET

/sms/messages/{id}

Get an SMS message by ID

PATCH

/sms/messages/{id}

Update a queued SMS message

DELETE

/sms/messages/{id}

Delete or cancel a queued SMS message

GET

/sms/messages

List SMS messages

POST

/sms/messages

Send an SMS message

GET

/sms/messages/{id}

Get an SMS message by ID

PATCH

/sms/messages/{id}

Update a queued SMS message

DELETE

/sms/messages/{id}

Delete or cancel a queued SMS message

Why though Jentic?

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

Credential isolation

Apideck application keys, x-apideck-app-id, and x-apideck-consumer-id values are stored encrypted in the Jentic vault. Agents receive scoped execution tokens and never see the raw Authorization value, even when sending SMS on behalf of an end user.

Intent-based discovery

Agents search by intent (for example 'send an sms' or 'send a verification code') and Jentic returns POST /sms/messages with its input schema, so the agent can call it without consulting Apideck or Twilio docs.

Time to first call

Direct Apideck SMS integration: half a day to wire auth and message status polling. Through Jentic: under 30 minutes — search, load schema, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Twilio API

Twilio direct API with deeper messaging features (Messaging Services, scheduled flows, MMS, WhatsApp) the unified SMS API does not surface.

Choose Twilio direct when the customer is Twilio-only and needs Messaging Services, Studio, or WhatsApp; choose Apideck SMS for write-once cross-provider code.

Alternative

MessageBird API

MessageBird direct API with deeper conversation and chat-channel features.

Choose MessageBird direct when you need their omnichannel conversation features; choose Apideck SMS for vendor-portable transactional SMS.

Complementary

Apideck Vault API

Vault sets up and stores the SMS provider connection the SMS API executes against.

Use Vault first to authorise the customer's Twilio/MessageBird/Vonage connection; then call POST /sms/messages scoped to that consumer.

FAQs

Specific to using SMS API API through Jentic.

What authentication does the Apideck SMS API use?

An apiKey scheme on the `Authorization` header with your Apideck application key. Through Jentic this value plus `x-apideck-app-id` and `x-apideck-consumer-id` are stored encrypted in the vault and injected at execution; the agent only ever holds a scoped token.

Can I send an SMS through Twilio, MessageBird, and Vonage with the same call?

Yes. POST /sms/messages takes a normalised payload — to, from, body, scheduled_send_time — that Apideck routes to whichever provider the customer's connection points at. The provider-specific message ID is returned as the response so subsequent GET /sms/messages/{id} calls work the same way across all providers.

What are the rate limits for the Apideck SMS API?

The OpenAPI spec does not publish per-endpoint rate limits. Apideck applies plan-based limits at unify.apideck.com plus the underlying provider's per-account messaging limits (Twilio's MPS limits, MessageBird's throughput tiers, etc.). See https://developers.apideck.com for your plan's gateway quota.

How do I send an SMS through Jentic?

Install with `pip install jentic`, then run the search query 'send an sms'. Jentic returns POST /sms/messages — load its schema, supply to, from (or sender_id), and body, then execute. The message lands on whichever provider the consumer has connected.

Can I cancel an SMS after it has been queued?

Yes — DELETE /sms/messages/{id} cancels a queued message before it is dispatched, and PATCH /sms/messages/{id} can update the body or scheduled-send time. Once a message has been handed to the underlying provider for delivery, cancellation is no longer possible — the provider's webhook will report the final status.

Does the SMS API support inbound messages?

GET /sms/messages can list inbound messages stored at the provider, but inbound delivery itself happens via the provider's webhook to your application — Apideck does not relay the inbound webhook through this API. Configure inbound handling at the underlying provider (Twilio, MessageBird, etc.).