Plivo · SMS
Plivo integration for SMS in a custom system
Plivo integration means your backend sends messages or calls via Plivo and records delivery on the case that triggered them. There is no reason to pick Plivo and [Twilio](/articles/integrations/twilio-integration) and [GatewayAPI](/articles/integrations/gatewayapi-integration). One telecom socket. Two if you split transaction and marketing on purpose. Shared rules for every SMS article: sender approved, consent on marketing, a log on transactions, never a CPR number in the SMS body, never a secret in the query string. Plivo is not “better”. It is the API you have keys for — or the one you picked after price in the countries you actually send to.
If you are already on MessageBird or Vonage, stay. A new logo in the middle of an app project is a new KYC and number project. Automating the message.
Shared rules for every SMS article
- Sender approved
- Consent on marketing
- A log on the transaction
- Never a CPR number in the SMS body
- Never a secret in the query string
One telecom socket
- The same retry and log
- One secret to rotate
- One truth about delivery
Two sockets on purpose
- Transaction vs marketing split
- Different senders and consents
- Not “to be safe”
What to do now
Say which login you have today. Have none, say country and volume. Then we pick one socket. Write it briefly.
FAQ about Plivo integration
Why pick Plivo over Twilio?
Because you have Plivo, or because the price in the countries you send to is better. Not because the API is “easier”.
Can we run Plivo and GatewayAPI at once?
Only if you split transaction and marketing on purpose. Otherwise it is two truths about delivery.
May the code sit in the URL?
No. Never a secret in the query string. Not even “just for test”.