Programmable SMS means your software sends and receives text messages through an API instead of a person typing into an app. You make an HTTP request, the provider handles the carrier connections, and replies and delivery reports come back to your server.

The term gets mixed up with two neighbors: the SMS gateway and the SMS marketing platform. They overlap, but they answer different questions. This guide sorts out the three, shows what a programmable setup includes and lists what to check before you pick one.

What programmable SMS is

Programmable SMS is texting as a building block. A developer calls an endpoint with a recipient and a message body, and the provider takes it from there. Inbound replies arrive as webhooks, so your code can react to them.

On Ready, a send looks like this:

POST https://api.tryready.com/v1/messages
X-API-Key: <key>
Idempotency-Key: <uuid>

{"to": "+12125550199", "body": "Your order #1042 has shipped.", "consent_attested": true}

That's the whole interface for one text. The to field is E.164, and consent_attested is your promise that the recipient agreed to be texted. The product can then be anything: order updates, appointment reminders, a CRM that texts leads for its customers. The text is a feature inside your app, not a separate tool your users log into.

How it differs from an SMS gateway

A gateway is a bridge, and an API is a product built on top of bridges. The two terms are often used loosely, so it helps to separate them.

An SMS gateway connects your system to the carrier network. It moves messages and little else. Some gateways are email-to-text addresses, some are hardware, and some are protocol-level connections for large senders. Registration, opt-outs, scrubbing and number management are yours to build. Our posts on what an SMS gateway is and gateway vs API vs email-to-SMS go deeper.

A programmable SMS API wraps that connection in documented endpoints, authentication, error codes and webhooks. The better ones add the compliance work around it.

How it differs from a marketing platform

A marketing platform is an app for people, and programmable SMS is a service for code. The platform gives a marketer a list, a composer, a scheduler and reports. The API gives a developer endpoints.

You can see the split in who does the work. With a platform, a marketer builds a campaign in a browser. With an API, your engineers decide when a text goes out and what triggers it. If your product needs to text on behalf of its own customers, a marketing platform's single login model usually doesn't fit, because each of your customers needs its own numbers, registration and opt-out list.

SMS gatewayProgrammable SMS APIMarketing platform
Built forMoving messagesDevelopers building texting into a productMarketers sending campaigns
InterfaceProtocol, email or hardwareREST endpoints and webhooksWeb app
Compliance workYoursVaries by providerMostly handled in the app
Multi-customer supportRareLook for sub-accountsUsually one account

What to look for

Pick on the details that cost you time later, not the headline price.

  • Registration support. US texting over local numbers needs 10DLC registration. Check whether the provider files it, how it prices it and whether you can do it by API. Our 10DLC explainer covers what's involved.
  • Sub-accounts. If you text for your own customers, each one should get separate numbers, registration and opt-outs.
  • Opt-out handling. STOP replies should be honored automatically and readable by API.
  • Idempotency. A retried request must not send twice.
  • Webhooks and error codes. You'll live in these when something fails.
  • Visible pricing. Look for a per-segment rate with carrier fees itemized separately.

Pricing and the segment math

Programmable SMS is billed per segment, not per message. One segment holds 160 GSM-7 characters, or 153 once a message splits into several parts. One emoji drops that to 70 (67 multipart), so a 140-character text with an emoji becomes 3 segments.

Ready charges $0.0075 a segment plus a $0.0045 carrier fee passed through at cost, and a received reply bills the same rate plus a $0.003 inbound carrier fee. Sending needs a card and a number of your own. Accounts opened before November 12, 2026 keep their signup prices, shown under Billing. The pricing page has the full list, and our SMS API pricing guide explains how to compare providers fairly.

Where Ready fits

Ready is a messaging API for software companies that text on behalf of their own customers: CRMs, vertical SaaS and other platforms. Each customer gets a sub-account with its own numbers and 10DLC registration, and TCPA and Do Not Call scrubbing, number validation, opt-out handling and webhooks are built in.

It isn't the right pick for everything. Ready sends over local 10DLC numbers and iMessage, and it doesn't sell toll-free numbers. If you need those, look elsewhere. For a platform that wants one REST API and compliance included, it's a fit. The API quickstart takes you from a key to a first send and a webhook.

Frequently asked questions

Is programmable SMS the same as an SMS API? In practice, yes. Programmable SMS is the category, and an SMS API is the interface you use to reach it.

Do I need to build my own compliance tooling? Only if your provider leaves it to you. Check registration, opt-outs and scrubbing before you commit.

Can a marketing platform replace an API? Only if people, not code, will trigger every text. A product that texts for its own customers needs an API.