Developer Center Introduction

Send your first text message with the Mobile Text Alerts API in under five minutes.

Welcome to the Mobile Text Alerts Developer Center

The Mobile Text Alerts API gives you programmatic control over everything you can do in the platform dashboard. Send SMS and MMS (images, multiple attachments, and contact cards), reach Apple devices with iMessage, and send rich RCS messages — all through a single POST /send endpoint that picks the right route for each recipient.

Beyond sending, the API covers the full lifecycle of a messaging program:

• Two-way messaging — receive replies, manage threads, and configure automated replies and keywords.

• Subscriber management — create, update, group, and segment subscribers, including custom attributes and adaptive groups that populate themselves over time.

• Scheduling and automation — schedule sends, build drip campaigns, and reuse message templates.

• Real-time events — webhooks for message sends, replies, delivery statuses, and opt-ins.

• Reporting — delivery analytics and message log exports.

API access is bundled with every subscription at no additional cost, including free trial accounts.

Not a developer? Every action described here is also available in the platform dashboard. The API is for teams who want to drive messaging from their own application.

Get Started: Send your first message with the API

If you are just getting started, the three steps below take you from no account to a delivered message. If you are already partway there, jump straight to your next milestone:

1

Create your free account

A free trial account includes API access and message credits, so you can build against the real API before you subscribe.

Create your free account

2

Generate an API key

In the platform dashboard, open Settings → Developer and click Generate a new key. Copy the key somewhere safe — it is shown only once.

Full walkthrough: Get an API Key.

3

Send your first message

Using the example requests below, replace the API key and recipient number.

Trial accounts and unverified numbers can only send templated content.

The following examples use global template 170. Once your sending number is approved, replace templateId with a custom message.

cURL

curl --location 'https://api.mobile-text-alerts.com/v3/send' \
  --header 'Authorization: Bearer 89fa747a-e01b-5940-99c2-4e96fa996258' \
  --header 'Content-Type: application/json' \
  --data '{
    "subscribers": ["[phone]"],
    "templateId": 170
  }'

Node.js

Requirements: Node.js 18+ (native fetch) and an MTA_API_KEY environment variable.

const response = await fetch("https://api.mobile-text-alerts.com/v3/send", {
  method: "POST",
  headers: {
    Authorization: `Bearer ${process.env.MTA_API_KEY}`,
    "Content-Type": "application/json",
  },
  body: JSON.stringify({
    subscribers: ["[phone]"],
    templateId: 170,
    // After approval, replace templateId with:
    // message: "Hello from the Mobile Text Alerts API! Reply STOP to end.",
  }),
});

console.log(await response.json());

Python

Requirements: pip install requests and an MTA_API_KEY environment variable.

import os
import requests

response = requests.post(
    "https://api.mobile-text-alerts.com/v3/send",
    headers={
        "Authorization": f"Bearer {os.getenv('MTA_API_KEY')}",
        "Content-Type": "application/json",
    },
    json={
        "subscribers": ["[phone]"],
        "templateId": 170,
        # After approval, replace templateId with:
        # "message": "Hello from the Mobile Text Alerts API! Reply STOP to end.",
    },
)

print(response.json())

A successful request returns a 200 with the message ID and a recipient count:

{
  "data": {
    "messageId": "uuid",
    "totalSent": 1,
    "totalFailedInternationalRecipients": 0
  },
  "message": "Message Sent to 1 Recipient."
}

Any number in the subscribers field that is not already on your account is automatically added as a new subscriber. To manage subscribers explicitly, see Add a Subscriber.

---

Authentication

Every request is authenticated with a bearer token — your API key — in the Authorization header:

Example bearer token:

Authorization: Bearer 89fa747a-e01b-5940-99c2-4e96fa996258

You can then confirm a key works:

Example verification request:

curl --location 'https://api.mobile-text-alerts.com/v3/auth/verify-api-key' \
  --header 'Authorization: Bearer 89fa747a-e01b-5940-99c2-4e96fa996258'

Response:

A valid key returns {"message":"API Key verified", ...}. A missing or revoked key returns a 401.

API Key Lifespan

Keys are scoped to a single account and never expire on their own, but they can be revoked from the dashboard at any time. For key generation, rotation, and the full authentication reference, see Get an API Key.

---

Mobile Text Alerts API Conventions

The following rules apply across every Mobile Text Alerts API endpoint.

Convention	Detail
Base URL	https://api.mobile-text-alerts.com/v3 — the version (v3) is part of the path, not a header.
Transport	HTTPS only. REST resources with standard GET, POST, PATCH, and DELETE methods.
Request bodies	JSON. All POST and PATCH requests must send Content-Type: application/json.
Response bodies	JSON, wrapped in a top-level data object with an accompanying message string.
Status codes	Standard HTTP codes: 200 success, 400 bad request, 401 unauthorized, 403 forbidden, 429 rate limited, 500 server error.
Errors	Every error returns: httpCode, message, timestamp, type, name, and a requestId to use when contacting support.
Phone numbers	E.164 format ([phone]) is the recommended format everywhere a phone number is accepted.
Lists	Paginated with page (0-indexed), pageSize (default 25, max 1000), sortBy, and sortDirection.
Rate limits	30 requests per minute per IP by default. Some endpoints override this with per-account limits.

---

SDKs and Tooling

TypeScript SDK

You do not have to manually create HTTP requests. The TypeScript SDK wraps every endpoint with typed requests and responses, IDE autocompletion, and per-endpoint error classes.

The latest version of the TypeScript SDK can be installed with npm:

npm install @mobiletextalerts/typescript-sdk

Example client configuration:

import { createClient, sendMessageFromApi } from '@mobiletextalerts/typescript-sdk';

const client = createClient({
  baseUrl: 'https://api.mobile-text-alerts.com/v3',
  headers: { Authorization: `Bearer ${process.env.MTA_API_KEY}` },
});

await sendMessageFromApi({
  client,
  body: { subscribers: ['[phone]'], message: 'Hello from the SDK!' },
});

More language libraries are in active development. See SDKs for the current list.

Build with AI assistants

Point your AI coding assistant at these docs and it can write integration code against the real, current API surface instead of guessing.

Tool	What it does	How to use it
Markdown pages	Any page is available as clean Markdown for pasting into a model's context	Append .md to any Developer Center URL, e.g. /getting-started/send-a-message.md
llms.txt	Indexed list of every page with descriptions	Give the URL to your assistant as a documentation map
llms-full.txt	The entire Developer Center in one file	Paste or fetch as full context for a model
Developer Center MCP server	Live documentation access from Claude, Cursor, VS Code, and other MCP clients	Connect to https://developers.mobile-text-alerts.com/~gitbook/mcp
Knowledge Base MCP server	Developer Center and Help Center content in one server	See the setup guide
Actions MCP server	Lets an AI assistant send messages and run account actions through the API	Connect with Claude

New to MCP? Start with MCP Servers.

---

Next Steps

Send messages

Customize sends with MMS, templates, personalization, scheduling, iMessage, and RCS.

Message Sending

Receive replies

Listen for inbound messages, delivery statuses, and opt-ins with webhooks.

Setting up Webhooks

Manage subscribers

Create, update, group, and segment your contacts, including bulk operations.

Manage Subscribers

Track delivery Poll delivery records or stream status changes in real time.

Check Delivery Status

Go to production

Choose a messaging route, register your brand, and plan around rate limits and errors.

Messaging Routes

Look up an endpoint

Full reference for every public endpoint, with interactive requests.

API REFERENCE

By use case

Start from what you are building rather than the endpoint you need to call.

• Generate and validate 2FA / MFA codes via SMS — issue verification codes, deliver them, and validate user input without building the state machine yourself.

More use case guides are on the way. If you are building something you do not see here, tell us what you need.