Programmable SMS means your code sends texts. Programmable messaging is the wider idea: one set of endpoints for every kind of message your product might send, whatever the channel underneath.

If you're a developer or a head of product choosing a provider, the useful question isn't "does it send texts?" Everyone does. It's what happens when your product needs a picture, a blue bubble, a reply, an opt-out or a second customer with their own numbers.

What "programmable messaging" means

The term has three parts.

Programmable. Everything a person could do in a messaging app, your software can do through an HTTP call: send, schedule, read replies, check opt-outs.

Messaging. More than plain text. SMS is the base. MMS adds pictures and other media. iMessage reaches iPhones with blue bubbles, typing indicators and reactions.

One interface. You learn one authentication scheme, one error format and one way to receive replies, instead of a separate integration for each channel.

If you're newer to the category, our programmable SMS explainer covers the SMS-only version and how it differs from a gateway.

The three channels, briefly

ChannelWhat it carriesGood forWatch for
SMSText, in 160-character segmentsAlerts, reminders, two-way repliesPer-segment billing, 10DLC registration
MMSPictures and other mediaReceipts, product photos, before-and-afterCarrier size limits, higher cost than text
iMessage (blue line)Text and photos to iPhonesConversations with people you already talk toLimits on new conversations, no Android reach

Each has rules of its own, and a good API makes the rules visible instead of hiding them. For MMS details, see our MMS API guide. For the blue line, see our iMessage API for business post.

What one API looks like on Ready

On Ready, sending an SMS is one request:

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}

The to field is a number in E.164 format. consent_attested is your promise that the recipient agreed to texts. The Idempotency-Key header makes a retry safe, so a timeout never sends the same text twice.

Add a media_url to send a picture, and it goes as an MMS. Set from to your account's own iMessage line, and the same endpoint sends through the blue line. If the contact isn't on iMessage, you get a refusal with fallback: sms and nothing is sent. Your code then resends without the line as from, and it goes as a regular text.

That's the main point of a single API. The channel is a field in the request, not a new product to integrate.

To send the same text to many numbers, POST /v1/messages/bulk takes a list of up to 100 recipients per call. Larger lists go in batches. The docs have every field.

How to evaluate a provider

Run the same checklist on every vendor you look at.

  1. Channels from one endpoint. Can you send SMS, MMS and iMessage without separate accounts or SDKs?
  2. Registration. US business texting over local numbers needs 10DLC registration. Does the provider file it for you, price it clearly and expose status by API? Our 10DLC explainer covers the background.
  3. Multi-customer support. If your product texts for its own customers, each needs its own numbers, registration and opt-out list. Look for sub-accounts, not a shared pool.
  4. Opt-outs. STOP replies should be honored automatically and readable by API.
  5. Idempotency and retries. A retry must never double-send.
  6. Webhooks. Inbound replies and delivery updates should arrive in a consistent shape across channels.
  7. Errors you can act on. A refusal should say why, so your code can respond.
  8. Visible pricing. Per-segment rates with carrier fees itemized, and any extra charges for compliance screening stated.

The last item is where surprises hide. Don't compare a headline rate to a bill. Compare the all-in cost for your own message mix.

What it costs

On Ready the Standard rate is $0.0075 a segment, plus a $0.0045 carrier fee on each sent segment and $0.003 on each received one. That rate doesn't include screening, the per-segment charge for Scrub lists and Number validation if you switch them on.

A blue line costs $99 a month per line, plus 6 cents a segment for each text sent. A reply to a blue line is also 6 cents a segment, and reactions are free. A blue line needs no 10DLC registration, so a business can start as soon as the line is set up. Texts to Android phones go from the account's regular number.

Sending also needs a card on file and a number of the account's own, at $2 a month. Every text is charged from the first one. An account can send up to 500 texts a month until its registration is approved. Accounts opened before November 12, 2026 keep their signup prices, shown under Billing. The pricing page has the full list.

Limits to design around

Every channel has a ceiling, and a product that ignores them breaks in production.

  • SMS segments are 160 characters, or 153 each once a message splits. One emoji drops that to 70 (67 multipart), so a 140-character text with an emoji becomes 3 segments.
  • Blue line lines can start up to 50 new conversations a day, and up to 2 texts go to someone until they reply. Photos wait until they reply. More new people a day means another line.
  • Campaigns and drip campaigns send from regular numbers, not the blue line.
  • Quiet hours apply by the recipient's area. An API text is held only if the window opens within 6 hours, otherwise your code sends it again once the window opens. See our post on handling quiet hours 409 errors.

Ready doesn't do RCS or WhatsApp. If you need them, you'll need another provider for those channels.

Frequently asked questions

Is programmable messaging the same as a CPaaS? A CPaaS is the platform category, usually covering voice, video and messaging. Programmable messaging is the messaging part.

Does iMessage replace SMS? No. A blue line reaches iPhones only, and a contact who isn't on iMessage needs a regular text.

Can my users each get their own numbers? Yes, through sub-accounts, each with its own numbers and registration.

Where do I start? The API quickstart takes you from a key to a first send and a webhook.

The takeaway

Judge a messaging API on how it handles the awkward cases: the contact who isn't on iMessage, the retry, the opt-out, the second customer. One endpoint for every channel only helps if the rules behind it are clear.

If that fits what you're building, start texting today and run the quickstart against a test key.