Verify
Sign-in codes, two-factor, and password resets. Short, time-sensitive, and tracked per attempt.
Your Acme sign-in code is 482193. It expires in 5 minutes.
SMS infrastructure
Send one-time codes, alerts, and product messages through one Rive account. Rive checks the sender, prices the message for its destination, routes it, and records the delivery receipt.
Today 14:02
01 · Send
Authenticate with a key, post the recipient, sender, and text. The response carries the message ID; the delivery report arrives on your webhook and in the ledger.
success flag and a request ID on every response.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" }
}
02 · Route
You decide who it is from, who gets it, and what it says. Rive does the rest, and the API retries through the next connector when one returns a retryable error.
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.
| Message | To | Status | Sent |
|---|---|---|---|
| msg_2Rk9wQ | +47 •••• 219 | Delivered | 14:02 |
| msg_9FhTzA | +46 •••• 044 | Delivered | 14:01 |
| msg_L0pxe3 | +45 •••• 281 | Awaiting receipt | 14:01 |
| msg_c4QvNm | +358 •••• 712 | Failed | 13:58 |
| msg_7bWdKs | +47 •••• 902 | Delivered | 13:57 |
03 · Track
Accepted, handed off, delivered, or failed with the reason. Search by number, sender, or message ID and open any row to see its lifecycle and cost.
04 · Identity
Sender names are requested in the console and checked before they carry traffic. Names that impersonate banks, authorities, or brands you do not own are refused, which protects your name as much as anyone's.
How review works05 · Spend
No platform fee and no seats on a standard account. The cost of each message is on its ledger row, so the bill always reconciles.
Available balance
$412.60
Illustration · example workspace
From the live price list, per accepted message.
06 · Operate
Balance, traffic, senders, keys, webhooks, and support live together. No vendor dashboards, no spreadsheets of routes.
Open a workspaceAvailable balance
$412.60
Messages, 24h
2,418
Delivered
97.9%
07 · Use
Sign-in codes, two-factor, and password resets. Short, time-sensitive, and tracked per attempt.
Your Acme sign-in code is 482193. It expires in 5 minutes.
Security notices, delivery updates, and appointment changes, written for people.
A new sign-in to your Acme account from Oslo. Not you? Reset your password.
Opted-in product messages on the same infrastructure, with the same receipts.
Reminder: your session is tomorrow at 10:00. Reply STOP to opt out.
How Rive is run
Read the compliance overview, GDPR information, and live status.
Pricing
A standard account has no platform fee and no seats. Top up the balance; each accepted message costs its destination rate.
Questions
Anything else goes to the support ledger, where a person answers.
One-time codes, transactional alerts, and opted-in product messages. Unsolicited marketing and brand impersonation are refused.
You request a sender in the console. It is reviewed before it can carry live traffic. Names that read as banks, authorities, or brands you do not own are refused.
No. You choose the sender, the destination, and the text. Rive prices the message for the destination and hands it to a connector for that route.
Each message has a status trail in the Messages ledger. Delivery receipts are also posted to your webhook, signed with your endpoint secret.
Prepaid. You top up by card or crypto, and each accepted message is charged at its destination rate. There is no platform fee on a standard account.
Create an account, request a sender, add funds, and call the API or send from the console.