How-to guide · Developers
API & MCP
Send texts from your own software with the Statxt Public API, or let an AI assistant like Claude work in your Statxt account through MCP. MCP (Model Context Protocol) is a standard way for AI apps to connect to tools.
How it works
- 1
Create a key
Make a test or live API key in the developer workspace.
- 2
Send a message
POST to /api/v1/messages with your key in the Authorization header.
- 3
Watch the results
Check request logs, or subscribe to webhooks for status updates.
- 4
Connect your AI
Add the Statxt MCP endpoint to Claude or another AI app and approve access.
STEP 01
Open the developer workspace
Go to Settings → Developers and click Open workspace. Everything for the API and MCP lives here.
- API Keys is where you create and revoke keys.
- Console lets you send test requests from your browser before you write code.
- Logs shows every API request and response.
- Recipes has copy-paste examples in TypeScript, Python and cURL. The full reference is at docs.statxt.com.
STEP 02
Create an API key
Open API Keys. Give the key a label you’ll recognize, pick the environment and scope, then click Create key.
- Test keys are for building. Test sends aren’t delivered to real phones and don’t use credits.
- Live keys send real texts. They’re available once your 10DLC registration is approved.
- Personal keys see only your data. Organization keys see your whole team’s data and can only be created by the owner.
- Copy the key right away. It’s shown only once.
STEP 03
Send your first message
Send a POST request to /api/v1/messages. Put your key in the Authorization header as a Bearer token.
- to is the recipient’s number. body is the text, up to 1,600 characters.
- Send from one of your Statxt numbers: give either from (the number, like +15125550177) or from_phone_number_id, not both.
- Personal keys can only send from a number assigned to you.
- Add an Idempotency-Key header so a retried request isn’t sent twice.
STEP 04
Check the response and logs
Statxt answers with 202 Accepted and the new message, including its id and status. Open Logs to see the request in your workspace.
- status moves through values like queued, sent and delivered, or failed and undelivered.
- Errors come back with a code and message. Look them up in the Errors tab.
- Want status updates pushed to you? Set up a webhook in the Webhooks tab.
STEP 05
Connect an AI assistant with MCP
Open the Statxt MCP page and pick your AI app. You don’t need an API key. You sign in to Statxt and approve access instead.
- Claude: copy the endpoint and add it as a connector in Claude.
- Codex: copy the install command and run it.
- Cursor or any other MCP client: use the endpoint https://mcp.statxt.com/mcp.
- Your AI app opens a Statxt consent screen. Review it and click Approve & reconnect.
STEP 06
Manage connected AI apps
See and remove AI app connections in Settings → Developers → MCP.
- Active connections lists every AI app you’ve approved.
- Click Disconnect to cut off an app. Connect again later to get a fresh approval.
- What the AI can reach depends on your role. Owners and admins get organization access. Managers and members get their personal workspace. Viewers get read-only access.
Pro tips
Get more out of API & MCP
Build with test keys
Test sends aren’t delivered and don’t use credits, so you can try your integration without texting real customers.
One key per integration
Give each app its own labelled key. If one leaks, revoke just that key without breaking the others.
Revoke right away
Click Revoke key on the API Keys page. Any app using that key stops working immediately.
Retry safely
Reuse the same Idempotency-Key when you retry a request. Statxt won’t send the message twice.
Try it in the Console
Use the API Console to build and send a request from your browser before writing any code.
Ask your AI to check first
Statxt’s MCP tools can preview a message and check compliance before sending. Ask your assistant to do that for anything customer-facing.
Common questions
How do I authenticate API requests?
Send your key in the Authorization header as Bearer <your key>. Keys start with intx_public_test_ or intx_public_live_.
Why can’t I create a live key?
Live keys need an approved 10DLC registration. Until then you can create test keys. Organization-scoped keys can only be created by the owner.
Do I need an API key to use MCP?
No. MCP uses OAuth. Your AI app sends you to Statxt to sign in and approve access, and you can disconnect it any time in Settings → Developers → MCP.
Where is the full API reference?
At docs.statxt.com. It covers every endpoint, including contacts, campaigns, templates and webhooks.
Last reviewed October 8, 2026. Names, phone numbers, contacts, and stats in the illustrations are fictional examples.
More guides
Try it in Statxt
Set up your workspace, bring your contacts, and send your first campaign today.