Send
Single and bulk sends from the API or the console, with the cost shown before the message leaves.
Platform
Rive handles sender review, routing, pricing, receipts, and signed callbacks behind one API and one console.
How it runs
The same path whether you send from the API or the console.
An API call, or a send from the console. Rive never needs a wholesale account from you.
Sender is approved. Balance covers the destination rate. A route is chosen. Retryable errors try the next connector.
The message leaves on the connector for that country. You never pick it.
The network delivers and reports. The receipt updates the ledger and is posted to your webhook.
For developers
One endpoint to send, one to read status, and signed events when the network reports back. Store the key as RIVESMS_API_KEY.
curl https://rivesms.com/api/v1/messages/send \
-H "Authorization: Bearer $RIVESMS_API_KEY" \
-H "Content-Type: application/json" \
-d '{"to":"+4790000219","from":"Acme","body":"Your Acme sign-in code is 482193."}'
const res = await fetch("https://rivesms.com/api/v1/messages/send", {
method: "POST",
headers: {
Authorization: `Bearer ${process.env.RIVESMS_API_KEY}`,
"Content-Type": "application/json",
},
body: JSON.stringify({ to: "+4790000219", from: "Acme", body: "Your Acme sign-in code is 482193." }),
});
import os, requests
requests.post(
"https://rivesms.com/api/v1/messages/send",
headers={"Authorization": f"Bearer {os.environ['RIVESMS_API_KEY']}"},
json={"to": "+4790000219", "from": "Acme", "body": "Your Acme sign-in code is 482193."},
)
{
"success": true,
"data": {
"id": "msg_2Rk9wQ…",
"status": "sent",
"to": "+4790000219",
"from": "Acme",
"cost": /* destination rate */,
"currency": "USD"
}
}
RiveSMS-Signature: t=1760000532,v1=8c1a…d4f7
{
"type": "message.delivered",
"data": { "id": "msg_2Rk9wQ…", "status": "delivered" }
}
In the product
Single and bulk sends from the API or the console, with the cost shown before the message leaves.
Rive prices each message for its country and hands it to a connector for that route. Retryable errors try the next connector.
Accepted, handed off, delivered, or failed with the reason, searchable by number and ID.
Sender names are reviewed before live traffic. Impersonation of banks, authorities, and other brands is refused.
Sent, delivered, and failed events, signed with HMAC-SHA256. Verify with RIVESMS_WEBHOOK_SECRET.
Bearer keys stored as a hash, with per-minute rate limits, request logs, and instant revocation.
Card and crypto top-ups, a balance ledger, and the cost on every message row.
Content checks before sending and an abuse address that reaches a person.
Tickets with the full conversation, answered by the operations team.