A secure SMS API protects the connection between your server and the API, and who is allowed to call it. It does not make the text itself private once it leaves for a phone, because SMS isn't end-to-end encrypted. If a vendor's page says "secure messaging API" and stops there, ask which of those two things they mean.

Here's an honest split of the security model for a texting API: what you can rely on, what you have to do yourself, and what no vendor can fix.

Three places a text can be exposed

Think of a text's life in three legs, from your server to the screen.

  • Leg one: your app to the API.
  • Leg two: the API and its provider to the carrier network.
  • Leg three: the carrier network to the recipient's phone, and the phone itself.

Security work you can control sits mostly in leg one, and in how you handle data after the text arrives. Legs two and three are the carrier network and the handset.

What the API connection protects

Calls to Ready go to https://api.tryready.com over HTTPS, so the request, including the phone number and the message body, is encrypted in transit between your server and the API. Authentication is an API key sent in an X-API-Key header. That key is what proves the call is yours, so it has to be handled like a password:

  • Keep it in a secret store or environment variable, never in client-side code or a repo.
  • Use a separate key per environment.
  • Rotate it when someone leaves the team, and after any suspected leak.

Our posts on API key security and rotation and API authentication and webhook signing go deeper on both. For inbound traffic, verify webhook signatures before trusting a payload, since anyone can post to a public URL. The exact scheme is in the Ready docs.

An Idempotency-Key header is not a security control, but it protects you from a retry sending the same text twice.

What SMS does not protect

SMS is not end-to-end encrypted. A text crosses carrier systems in a form those systems can read, and it lands on a phone whose lock screen may show it to anyone nearby. Messages can be stored by carriers and by the sender's and recipient's own systems. So a texting API can be well run and the channel is still not a private one. Our encrypted text message post covers this in more detail.

There's one wrinkle worth knowing. The blue line sends as iMessage, which shows blue on iPhones with the business's name and photo. A text to an Android phone goes out from the account's regular number as SMS. Whether a given conversation is protected by Apple's own encryption between devices is a question for Apple's documentation, and we won't promise it for you. Treat the blue line as a better experience, and not as a security guarantee. See the iMessage docs.

What never to put in a text

Don't sendSend this instead
Passwords or password reset links that don't expireA short-lived code or a link that expires fast
Full card numbers, SSNs, account numbersThe last four digits at most, or "log in to view"
Diagnoses, medications, test results"Your results are ready, please log in."
Anything you'd mind seeing on a lock screenA pointer to a login page

Ready is not HIPAA compliant and doesn't sign BAAs, so keep protected health information out of texts entirely. PHI-free reminders are fine. See PHI in the message body for examples.

Security checklist for your integration

  • API key in a secret store, rotated on a schedule you can name.
  • HTTPS only, and no keys in mobile or browser code.
  • Webhook signatures verified on every inbound call.
  • Logs that don't store full message bodies longer than you need them.
  • Opt-outs honored: check GET /v1/opt-outs/:phone when you send from another tool.
  • Message content reviewed against the table above.

The first four are engineering work. The last two are about the content you choose to send.

Wrapping up

A secure texting API gets you an encrypted connection to the API, an authenticated caller and signed webhooks. It can't make SMS private, and it can't stop you from texting something sensitive. Design your messages as if a stranger might read them, because sometimes one will. If you want to see the request shapes, the messages docs are the place to start, and signup is open.

Frequently asked questions

Is SMS encrypted?

Not end to end. Traffic to a good API is encrypted in transit over HTTPS, but the text itself is readable by the carrier systems it passes through.

Can I text patient information securely through an SMS API?

Not through Ready. It isn't HIPAA compliant and doesn't sign BAAs, so keep diagnoses, medications and test results out of texts.

Does the blue line make texts secure?

It improves the look of the conversation on iPhones. Don't treat it as a security guarantee, and check Apple's documentation for what its encryption covers.

How do I secure webhooks from a texting API?

Verify the signature on every request before acting on it, and reject anything that fails. See the authentication and webhook signing post for the pattern.