SMS8

SMS8 API for developers.

Send SMS and MMS through the SMS8 API and they leave your own phone. One API key for every endpoint, webhooks for replies and delivery reports, an SDK for Node, ready-made PHP and C# classes, and an MCP server for AI agents.

SMS8: Copy your key, send with one request and track delivery with webhooks.
Get started in one command
npm install sms8-sdk

Claude Desktop: Settings, Connectors, Add custom connector

How the API works

Every request goes to app.sms8.io. You send a simple form post with your API key and the fields you need. You get JSON back, with a clear success flag and the message details.

Behind it, the message goes to an Android phone you paired, and that phone sends it from its own SIM. Replies and delivery reports come back to you the same way.

There is no artificial rate limit on the API. Real throughput depends on your SIMs. Add phones or use a dual-SIM phone to send more.

What you can do

One endpoint per job. The full reference lists every field.

01

Send SMS and MMS

Send one message, a batch to many people, or a broadcast to a saved contact list. Add image links for MMS. Schedule a send for later, or set it to jump the queue.

02

Choose the sender

Send from one phone and SIM, rotate across all your phones, or pick a random one per message to spread the load.

03

Read and resend

Look up any message by ID to see its status. Put failed messages back in the queue with one call.

04

OTP codes

Send a one-time code and check what the user typed. Codes are limited per phone number per day to protect recipients.

05

Devices and contacts

List your paired phones and their SIMs. Create or update contacts with a name, tags and custom fields.

06

USSD

Send a carrier USSD code, like a balance check, from a paired phone and read the reply.

Authentication and responses

One key per account, the same answer shape on every call.

01

Where the key lives

Your key is shown on the API page of your SMS8 dashboard. Treat the key like a password and keep it on your server, not in a public web page.

02

How to send it

Put it in the X-Api-Key header, as shown in the OpenAPI file. A bearer token in the Authorization header or a form field called key also work.

03

What comes back

JSON with a success flag. On success you get the message or record. On failure you get an error with a code and a short message.

04

Check the flag

Some errors, like bad fields or no credits left, come back inside a normal response. Read the success flag before you trust the result.

05

When the key is wrong

A missing or invalid key returns 401. Fields that are missing or malformed return 400.

Endpoints at a glance

All under app.sms8.io. The OpenAPI file has the exact fields for each one.

PathMethodWhat it does
/api/v1/messagesPOSTSend an SMS or MMS to one person or a batch
/api/v1/messages/readPOSTList sent and received messages, filtered by number, direction or date
/api/v1/messages/resendPOSTRetry a message that failed, by its ID
/api/v1/devicesGETList paired phones with battery, signal, SIMs and last seen time
/api/v1/contactsPOSTCreate or update a contact with tags and custom fields
/api/v1/ussd/sendPOSTRun a USSD code from a paired SIM and get the carrier answer
/api/v1/ussd/listPOSTList your recent USSD sessions

Sending a message, field by field

Only the number and the text are required. Everything else has a default.

01

Number and text

The number goes in international format, like +14155550100. The text can be up to 1,000 characters and can use merge tags such as {first_name}.

02

SMS or MMS

The type is sms by default. For MMS, add public HTTPS image links. SMS8 resizes each image to 1,280 pixels before sending.

03

Which phone sends it

Name one or more device IDs and a SIM slot, where 0 is SIM 1 and 1 is SIM 2. Leave them out and your default phone sends.

04

Rotation

Set the option to rotate across all your phones, or across every SIM on every phone. A random phone per message is also possible.

05

Jump the queue

Mark a message as priority and it goes ahead of others waiting on that phone. Useful for alerts and codes.

06

What you get back

A message ID for later lookups, the phone and SIM that took it, and the time it was queued. The status then moves through queued, sending, sent, delivered or failed.

Webhooks

Register a URL and SMS8 posts events to it as they happen. Each webhook picks its own events and gets its own signing secret, so you can check every request is really from SMS8.

01

Received

A reply or new message arrived on one of your phones. The one most CRM setups need.

02

Sent

Your phone took the message and queued it on its SIM. Good for audit logs.

03

Delivered

The recipient's carrier confirmed delivery.

04

Failed

The message could not be sent after retries, for example a bad number or no signal.

05

USSD reply

The carrier answered a USSD code you sent.

06

Phone paired

A new phone joined your account.

Signed, retried and logged

Every webhook request carries an X-Signature header. It is an HMAC-SHA256 hash of the raw request body, made with that webhook's own secret, not your API key. Compute the same hash on your server, compare the two with a constant-time check, and drop anything that does not match.

Your receiver must use HTTPS and should answer with a 2xx status within 10 seconds. If it does not, SMS8 tries again on a schedule that grows from a few minutes up to 30 days. Each attempt shows in the deliveries log with the status and response, and you can retry any row by hand.

Respond first and do slow work later, like CRM lookups or AI classification. Use the message ID as a unique key so a retried event is never processed twice.

For AI agents

The SMS8 MCP server at mcp.sms8.io lets Claude, Cursor and other AI tools send SMS, send and check OTP codes, read messages, list your phones and set up webhooks.

It uses the same API key, sent as a bearer token. Add it to your AI tool once and your agent can text from your number.

Common questions

Still unsure? We answer fast.

Send your API key with every request. You find it on the API page of your dashboard. The MCP server takes the same key as a bearer token.

The API has no artificial limit. Your SIMs set the real pace. For big sends, add phones or set a delay between messages in your settings.

Subscribe a webhook to delivered and failed events, or look the message up by ID.

Yes. Set the type to MMS and add public image links. SMS8 resizes the images before sending.

Yes. The current endpoints live under /api/v1, and the older URLs keep working for existing apps.

No. Each webhook has its own signing secret, set when you create it. Your API key never leaves your requests to SMS8.

Events wait in the retry queue and SMS8 keeps trying for up to 30 days. You can also resend any delivery from the log once you are back.

Yes. Import the OpenAPI file into Postman, Insomnia or a code generator to get every endpoint and field.

Yes. Pass a device ID and a SIM slot, or let SMS8 rotate across your phones and SIMs to spread the load.

Guides and comparisons

Go deeper on this topic.

Compare

SMS API: Send SMS From Your Own Phone Number

The SMS8 SMS API sends SMS and MMS from your own Android phone. One POST with an API key, signed webhooks for replies, and examples in 5 languages.

Compare

Send SMS With Python: SMS API From Your Own Phone

Send SMS and MMS from Python with requests and the SMS8 API. Copy-paste code for bulk sends, replies, signed webhooks and retries, from your own phone.

Compare

Send SMS With Node.js: SMS API From Your Own Phone

Send SMS and MMS from Node.js with the sms8-sdk npm package or fetch. Copy-paste code for bulk sends, replies, signed webhooks and safe retries.

Compare

Send SMS With PHP: SMS API From Your Own Phone

Send SMS and MMS from PHP with curl or Laravel and the SMS8 API. Copy-paste code for bulk sends, replies, signed webhooks and retries, from your phone.

Compare

Send SMS With C#: .NET SMS API From Your Own Phone

Send SMS and MMS from C# and .NET with HttpClient and the SMS8 API. Copy-paste code for bulk sends, replies, signed webhooks and retries, from your phone.

Compare

Send SMS With curl: SMS API From the Command Line

Send SMS and MMS with one curl command and the SMS8 API. Copy-paste requests for bulk sends, reading replies, checking webhook signatures and retries.

Nov 2026

SMS API for Developers: 2026 Guide With Code

Send and receive SMS with Node, Python, PHP and curl. Webhooks with HMAC signature checks, error handling, safe retries and pacing, from your own phone.

Nov 2026

Send SMS From the Terminal: sms8 CLI Guide 2026

Send SMS from the command line with the sms8 CLI or curl. Install sms8-sdk, script cron reminders and deploy alerts, and run it in CI with a secret key.

Nov 2026

Send MMS With an API From Your Own Phone (2026)

Send MMS pictures through an API from your own Android phone. How MMS differs from SMS, safe file sizes, the SMS8 API call, and cost vs per-MMS pricing.

May 2026

Webhook vs Polling for Incoming SMS: Which to Use

Webhook or polling for incoming SMS? Use webhooks with a slow polling backstop. Latency, HMAC signatures, retries and idempotency in PHP, Node, Python.

Nov 2026

Ecommerce SMS API: Order and Cart Texts

An ecommerce SMS API for 2026: order, shipping and cart texts from your own number through the SMS8 API or WooCommerce plugin, flat price, unlimited SMS.

Nov 2026

SMS API for SaaS: Add Texting to Your App in 2026

Add SMS to your SaaS in 2026: notifications, OTP codes and two-way replies through one API, from your own phones, on a flat plan with no per-message bill.

Nov 2026

SMS API Pricing in 2026: Per-Message vs Flat Plans

How SMS APIs charge in 2026: per segment, carrier fees, number rental and 10DLC. See real totals and why a flat plan with unlimited messages costs less.

Nov 2026

Two-Way SMS API: Send and Receive Texts in 2026

Build two-way SMS in 2026: send texts, get every reply on a signed webhook, answer from code or a shared inbox, from your own number on a flat SMS8 plan.

Send your first API call

Create an account, pair a phone and copy your API key. Your code can send in minutes.