Connect your own Plivo account
A high-value US-centric provider with a Twilio-style API, which makes it a common choice for cost-sensitive high-volume traffic.
What you need from Plivo
Gather these in the Plivo portal first. The connection form asks for exactly these fields and nothing more.
| Field | What it is |
|---|---|
| apiKey | Auth ID. Plivo calls this the Auth ID. |
| apiSecret | Auth Token. Paired with the Auth ID. |
Credentials are sealed with AES-256-GCM and the console only ever shows a masked value afterwards. Plaintext is never written to logs and never sent back to the browser.
What we configure on the connection
- Sender numbers. Plivo numbers you own.
- Default send pacing: 5 messages per second. This is a conservative starting point, applied per connection, and you can change it at any time. Your real ceiling is set by Plivo — check your account quota and raise the value to match.
Why teams pick Plivo
- Lower unit cost for high-volume US traffic
- Twilio-style API surface, so migrations are mostly mechanical
- Works well as a second route under a Twilio primary
Worth knowing
- Our default pacing is conservative. Plivo throughput depends on your account level and number type — raise it once you know your ceiling.
What stays on your side
These are yours to hold — and that is the point of bringing your own account: the relationship, the rates and the compliance stay in your name, not ours.
- Account approval, credit checks and arrears
- Sender ID, number and short-code registration for each destination
- Local telecom and privacy compliance in the countries you send to, including opt-out rules
- The quotas and rate limits Plivo grants your account
Next
Whaleal Messaging currently offers self-service connections to 6 SMS providers. Underlying the SMS channel is an adapter library covering 33 providers; the ones outside this list are unlocked on request rather than self-service.