MessageBird SMS API
Browse all Messagebird APIs49
AI ReadinessFoundational (D+)49/100
Agent-ready OpenAPI document · curated by JenticCommunicationsSms MessagingapiKey4 EndpointsREST
Know of an official OpenAPI document? Contribute it →
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://jentic.com/install.sh?src=apis&api=%2Fapis%2Fmessagebird.com%2Fmessagebird-sms-api" | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fmessagebird.com%2Fmessagebird-sms-api" | 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 your Jentic One instance 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
Jentic AI Readiness Score
This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.
M
MessageBird SMS API
- Foundational (D+)49/100
80
Foundational Compliance68
Developer Experience & Jentic Compatibility24
AI-Readiness & Agent Experience94
Agent Usability50
Security100
AI DiscoverabilityPowered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.0
Show dimension breakdown
80
Foundational Compliance
Base layer of spec validity and structural soundness.
Grade: A-Signals: 4
98%
Lint Results
Aggregated quality score from linter diagnostics, weighted by severity.
100%
Resolution Completeness
Percentage of `$ref` references that resolve successfully.
100%
Specification Validity
Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).
21%
Structural Integrity
Structural correctness score based on schema issues using logarithmic dampening.
68
Developer Experience & Jentic Compatibility
Clarity, completeness, and ingestion readiness for developers and tooling.
Grade: B+Signals: 4
50%
Example Density
How richly the API is illustrated with examples.
78%
Example Validity
Percentage of examples that conform to their schemas.
44%
Response Coverage
Percentage of operations with complete response definitions (success, client error, server error).
100%
Tooling Readiness
Health of API ingestion, bundling, and resolution within Jentic pipelines.
24
AI-Readiness & Agent Experience
Semantic breadth, depth, and agent comprehension for AI systems.
Grade: FSignals: 4
15%
Description Coverage
Coverage of descriptions across API elements.
0%
Error Standardization
Coverage of RFC 9457 Problem Details for error responses.
0%
OperationId Quality
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
80%
Summary Coverage
Coverage of summaries across operations/tags/info.
94
Agent Usability
Functional utility, complexity comfort, and AI orchestration readiness.
Grade: A+Signals: 1
94%
Complexity Comfort
Agent comfort level based on API operational and structural complexity.
50
Security
Trust, risk posture, and security compliance.
Grade: C-Signals: 1
50%
Authentication Strength
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
100
AI Discoverability
Findability, semantic richness, and reasoning readiness.
Grade: A+Signals: 1
100%
Descriptive Richness
Clarity and depth of descriptions across API elements.
Score it yourself
Every API in the directory is allowlisted, so you can re-score it with no key required.
npx @jentic/api-scorecard-cli score <openapi-url>Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the MessageBird SMS API by hand means placing your AccessKey in the Authorization header on every request against the rest.messagebird host, shaping the message body, and handling retries yourself. Through Jentic you install once, import the SMS API from the API Directory, store the AccessKey once, and your agent calls it.
Permission scoping
The SMS API takes the recipients and text in the request body when sending, with the message id appearing in the path only for reads and deletes (/messages/{messageId}), so scope your agent by operation: limit it to sending and listing messages, and the delete operation stays out of reach unless you add it.
Credential isolation
Your MessageBird AccessKey is stored once, encrypted, by your own Jentic One instance and injected into the Authorization header at execution time. It never enters the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'send an SMS' or 'look up a message record', and Jentic returns the matching operation such as POST /messages with its input schema so the agent calls the right endpoint without browsing the reference docs.
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 with Jentic One, the self-hosted execution layer.
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 your Jentic One instance 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.
Can I limit what my agent is allowed to do with the MessageBird SMS API?
Yes. Because you run Jentic One yourself, your own rules decide which of the four operations the agent may call, so you can allow it to send messages with POST /messages and list them with GET /messages while keeping the rest off limits. The DELETE /messages/{messageId} operation that removes a stored record stays out of reach unless you explicitly grant it, and the same applies to the GET /messages/{messageId} lookup. Your MessageBird AccessKey is held by your Jentic One instance and injected at execution time, so the agent never sees the credential or gains access to operations you have not enabled.
GET STARTED