For most product teams, an HTTP (REST) SMS API is the right choice. You send a JSON request, get a JSON response, and use the same tools you already use for every other API. SMPP is a persistent, binary protocol built for very high throughput between carriers and large aggregators, and it makes sense mainly when you're the one running that kind of pipe.
Ready exposes a REST API only. If you need an SMPP bind, that's a different kind of vendor. This post explains the difference so you can pick on facts instead of habit.
What SMPP is and what HTTP is
SMPP (Short Message Peer-to-Peer) is a long-lived TCP connection. Your system "binds" to a server, then streams messages and receives delivery receipts over that open session. It was designed for telecom systems talking to each other.
An HTTP SMS API is a normal web request. You call an endpoint, you get an answer. There's no session to hold open and no protocol library to maintain.
Side by side
| Question | HTTP / REST | SMPP |
|---|---|---|
| Connection | One request per call | Persistent bind |
| Tooling | Any HTTP client, curl, Postman | An SMPP library and a bind to keep alive |
| Failure handling | Retry the request | Reconnect, rebind, track windowing |
| Delivery updates | Webhooks or polling | Receipts over the session |
| Debugging | Read the request and response | Read protocol logs |
| Typical user | Product teams, SaaS, CRMs | Large aggregators, carrier-side systems |
Why most product teams want HTTP
You already know how to do it. Authentication is a header, retries are a wrapper, and a failed call is an error you can log. Idempotency is one header, so a retried send never goes out twice. Our idempotency post shows why that matters.
HTTP also scales with how your product works. Your app sends when something happens, such as an appointment booking, not in a constant stream. A short request per event matches that shape.
You also skip operating a connection. With SMPP, someone owns keeping the bind alive, handling dropped sessions and pacing sends to the server's window. That's real engineering time that isn't your product.
When SMPP makes sense
SMPP earns its keep when you send at very high, steady volume and you control the pipeline. Think of a company that routes traffic for many downstream senders, where saving per-message overhead matters and an engineer is assigned to the connection. It can also fit when a legacy system already speaks SMPP and you'd rather not rewrite it.
If none of that sounds like you, SMPP is complexity without a payoff. Also note that the protocol isn't the bottleneck for most senders. Carrier throughput limits per registered campaign are, and they apply however you connect. Our rate limits post covers that.
What Ready exposes
Ready is a REST API. Base URL https://api.tryready.com, auth in an X-API-Key header. Sending one text looks like this:
POST /v1/messages
X-API-Key: <key>
Idempotency-Key: <any UUID>
{"to": "+12125550199", "body": "Your order #1042 has shipped.", "consent_attested": true} To text many numbers in one call, use POST /v1/messages/bulk with up to 100 recipients per call, and split larger lists into batches. Read messages with GET /v1/messages, check opt-outs with GET /v1/opt-outs/:phone, and create sub-accounts with POST /v1/sub-accounts. The API quickstart walks through a key, a first send and a webhook.
A worked example with stated assumptions
Assume you send 40,000 one-segment texts a month with HTTP and one engineer spends two hours a month on the integration. The text cost is 40,000 x ($0.0075 + $0.0045) = 40,000 x $0.012, an all-in figure that excludes screening. Protocol choice doesn't change that line. What changes is the engineering time: an SMPP bind adds work for connection handling that an HTTP call doesn't. Accounts opened before November 12, 2026 keep their signup prices, shown under Billing.
Ready's all-in prices per segment include the carrier fee but not screening: Scrub lists and Number validation, the two switches in Settings under Compliance, each add $0.003 per segment when switched on, shown as screening on your bill, and both are off by default. Unless you turn the opt-out footer off, the first text to each contact, and one again from time to time, also gets "Reply STOP to opt out" and your business name if the message does not already have them, so a text close to the segment limit can bill one more segment.
Next step
If you're building a product that texts on behalf of customers, start with HTTP, put a retry wrapper and an idempotency key around it, and revisit protocols only if you hit a wall you can name. The SMS API integration guide is a good place to begin, and pricing lists the full rates.
Frequently asked questions
Is an HTTP SMS API slower than SMPP?
Per message, an HTTP call carries more overhead. For most products that's invisible, because carrier throughput limits on a registered campaign set the real ceiling.
Does Ready support SMPP?
No. Ready exposes a REST API only, with webhooks for inbound messages and updates.
Can I send in bulk over HTTP?
Yes. Ready's bulk endpoint takes up to 100 recipients per call, and you batch larger lists.
Do I still need 10DLC registration with HTTP?
Yes. Registration is about the carrier rules for US business texting, not how you connect, so it applies either way.