Moving an SMS integration is mostly a mapping exercise. Your Plivo code sends a message, receives replies on a webhook, tracks opt-outs and owns a pool of numbers. Ready has an equivalent for each, but a few of them live in a different place. Do the mapping before you touch production.
We haven't tested your code, and Plivo's API changes, so treat the left column as a prompt to check your own integration rather than a reference to Plivo.
The mapping
| In your Plivo integration | On Ready |
|---|---|
| Send one message | POST /v1/messages with to, body and consent_attested |
| Send to a list | POST /v1/messages/bulk, up to 100 recipients per call |
| Retry safety | Idempotency-Key header, one UUID per message |
| Message from a chosen number | Optional from; leave it out and Ready picks the number |
| Inbound reply webhook | A webhook you register; see the quickstart |
| Your own opt-out table | Opt-outs applied by Ready; read with GET /v1/opt-outs |
| Brand and campaign registration | One Registration line per customer, in the app or by API |
| Number rental | Numbers bought in the app, $2 a month each |
Fields beyond those aren't listed here on purpose. The messages API docs and the quickstart are the source for request details.
Things that behave differently
- Consent flag. Ready asks you to attest consent on each API send. Until January 20, 2027 (UTC), a send without
consent_attestedstill goes out with a warning and leaves no attestation. From January 20, 2027 it's refused with a 403. - Opt-outs are checked for you. A number on the Ban list is refused up front and not charged. You can stop paying for your own check on every call, but keep your table until the import is done.
- Quiet hours. An API text outside the recipient's window is held only if the window opens within 6 hours, otherwise it's refused with a 409 you handle. See handling the 409.
- Registration is per customer. If you run many tenants on one registration today, plan a registration per tenant.
A cutover order that avoids dead air
- Register on Ready first. Most approvals take 2 to 7 days. Until the registration is approved, an account sends up to 500 texts a month.
- Export your opt-outs from Plivo and your own table, and import them before any send.
- Send test messages from a Ready number to your team.
- Move traffic gradually, one tenant at a time, behind a flag.
- Port numbers last, if at all. Use the port checklist, which applies to any provider, and see why a STOP list doesn't travel with a number.
What you gain and what you give up
You gain registration, opt-outs, quiet hours and screening handled in the send path, and a dashboard and inbox. You give up Plivo's wider voice and messaging catalog and, at high volume, possibly a lower raw per-segment rate. Ready's Standard rate is $0.0075 plus a $0.0045 carrier fee, with no volume discount.
If you're comparing first, read Plivo vs Ready for SaaS texting.
Frequently asked questions
Do I need to rewrite my webhook handler?
Probably some of it. Payload shapes differ, so adapt the parsing and keep the idempotency logic.
Can I run both providers during the move?
Yes, and you should, tenant by tenant.
The practical takeaway
Map, import opt-outs, test, then move one tenant at a time. Sign up and send a test message before you commit.
Accounts opened before November 12, 2026 keep their signup prices, shown under Billing.