MessageBird SMS API
Browse all Messagebird APIs★ Only Publicly Available OpenAPI DocumentCommunicationsSms MessagingapiKey4 EndpointsREST
For Agents
Send SMS messages and inspect or delete previously sent message records via MessageBird's REST surface, in 4 endpoints.
Use for: Send an SMS to a customer phone number, Retrieve a previously sent SMS by ID, List all SMS messages sent today, Check whether an SMS was accepted by the gateway
Not supported: Does not handle voice calls, WhatsApp, intent classification, or NER — use for SMS sending and message record management only.
Jentic publishes the only available OpenAPI specification for MessageBird SMS API, keeping it validated and agent-ready. The MessageBird SMS API sends and manages SMS messages through MessageBird's global mobile network, returning delivery metadata for each send. Agents can dispatch a message, list previously sent messages, look up a single message by ID, and delete a stored message record from the same compact surface. Authentication uses MessageBird's `AccessKey` scheme and the API is suitable for transactional SMS, OTP delivery, and outbound notifications.
Install Jentic One Beta
Connect the MessageBird SMS API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the MessageBird 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.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
1
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 | sh2
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 instanceJentic 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 MessageBird SMS API.
Send a transactional SMS to a customer phone number with a custom originator name
List recently sent SMS messages for a status reconciliation sweep
Look up a specific message by ID to confirm it left the gateway
Delete a stored SMS message record once it has been processed downstream
Dispatch one-time passcodes (OTP) over SMS for account verification flows
Use Cases
Patterns agents use MessageBird SMS API for, with concrete tasks.
★ Transactional SMS Delivery
Send order confirmations, shipping updates, and appointment reminders by posting a message to the SMS endpoint with the recipient and body. The API returns a message ID and gateway acknowledgment, which the workflow can store for later auditing. This is the core path for any product that needs to reach customers reliably on their phone.
POST to /messages with the recipient number, originator, and message body, then store the returned message ID against the order record
OTP and Two-Factor Codes
Generate a numeric one-time passcode in your application, send it via the SMS endpoint, and verify the user-entered code on submission. MessageBird handles delivery across carriers and the response confirms the message was accepted by the gateway. Pair this with a short TTL and a per-user rate limit to keep the flow secure.
POST a 6-digit OTP to /messages addressed to the user's phone and persist the code with a 5-minute expiry for verification
Delivery Audit and Cleanup
List previously sent messages and look up individual records by ID to reconcile delivery against an internal database. After audit and reporting, the DELETE endpoint removes the stored record from MessageBird so retention is managed centrally. This is useful for compliance regimes that require message log purging on a schedule.
GET /messages, reconcile each message ID against the internal log, then DELETE /messages/{messageId} for records older than the retention window
AI Agent Integration via Jentic
An AI agent uses Jentic to discover the SMS API by intent search ('send an SMS'). Jentic returns the POST /messages operation with its input schema (recipient, originator, body) so the agent can dispatch a message in a single load-and-execute step. The MessageBird AccessKey is held in the Jentic vault and never enters the agent's prompt.
Use Jentic to search 'send an SMS', load the POST /messages schema, and execute it to send a delivery notification to the customer
Key Endpoints
4 endpoints — jentic publishes the only available openapi specification for messagebird sms api, keeping it validated and agent-ready.
METHOD
PATH
DESCRIPTION
POST
/messages
Send an SMS message
GET
/messages
List sent SMS messages
GET
/messages/{messageId}
Get a single message by ID
DELETE
/messages/{messageId}
Delete a stored message record by ID
POST
/messages
Send an SMS message
GET
/messages
List sent SMS messages
GET
/messages/{messageId}
Get a single message by ID
DELETE
/messages/{messageId}
Delete a stored message record by ID
Why Jentic?
Three things that make agents converge on Jentic-routed access.
Credential isolation
MessageBird AccessKey API keys are stored encrypted in the Jentic vault (MAXsystem). The `AccessKey` value is injected into the `Authorization` header at request time and never enters the agent's prompt.
Intent-based discovery
Agents search by intent (e.g. 'send an SMS') and Jentic returns POST /messages with its input schema, so the agent calls the right endpoint without browsing docs.
Time to first call
Direct MessageBird integration: half a day for auth and a basic send flow. Through Jentic: under 15 minutes — search, load schema, execute.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using MessageBird SMS API through Jentic.
Why is there no official OpenAPI spec for MessageBird SMS API?
MessageBird does not publish an OpenAPI specification for its SMS API. Jentic generates and maintains this spec so that AI agents and developers can call SMS sending 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 MessageBird SMS API use?
An API key in the `Authorization` header, prefixed with the word `AccessKey` (for example `Authorization: AccessKey w223tVQTcLO4ufBTuJxjvzwJ22`). Through Jentic the key is held in the MAXsystem vault and never appears in the agent's prompt.
Can I look up the status of a specific SMS after sending?
Yes. Capture the message ID returned from POST /messages and call GET /messages/{messageId} to retrieve the stored record, which includes the gateway acknowledgment fields.
How do I delete an old SMS record?
Call DELETE /messages/{messageId} once the record has been processed and is past your retention policy. Listing is available via GET /messages so you can iterate and prune programmatically.
How do I send an SMS through Jentic?
Search Jentic for `send an SMS`, load the POST /messages operation, and execute it with the recipient, originator, and body fields. Jentic returns the gateway response including the message ID.
Are there published rate limits?
The OpenAPI spec does not declare quantitative rate limits. Check your MessageBird account dashboard for the limits attached to your plan and design retry-with-backoff into the workflow before sending bulk traffic.
GET STARTED