Skip to content

SMS infrastructure

Messages that arrive. Receipts that prove it.

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.

  • Prepaid, no seats
  • Reviewed senders
  • Signed webhooks
  • Operated from Norway
14:02
AC Acme Text message

Today 14:02

Your Acme sign-in code is 482193. It expires in 5 minutes.

Delivered

msg_2Rk9wQ… Delivered
  1. 14:02:11.204 Accepted POST /v1/messages/send
  2. 14:02:11.231 Priced Norway · destination rate
  3. 14:02:11.388 Handed off Route chosen by Rive
  4. 14:02:12.917 Delivered Receipt from the network
To
+47 9•• •• 219
From
Acme
Segments
1
Webhook
message.delivered · 200
Illustration · example values

01 · Send

One request. A receipt for every message.

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.

  • Bearer keys per environment, revocable from the console.
  • Plain JSON with a success flag and a request ID on every response.
  • Signed events for sent, delivered, and failed.
Sending messages
Request
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."},
)
Responsemessage accepted
{
  "success": true,
  "data": {
    "id": "msg_2Rk9wQ…",
    "status": "sent",
    "to": "+4790000219",
    "from": "Acme",
    "cost": /* destination rate */,
    "currency": "USD"
  }
}
POST to your endpointmessage.delivered
RiveSMS-Signature: t=1760000532,v1=8c1a…d4f7
{
  "type": "message.delivered",
  "data": { "id": "msg_2Rk9wQ…", "status": "delivered" }
}

02 · Route

Routing stays inside Rive.

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.

  1. 01

    Your product

    An API call, or a send from the console. Rive never needs a wholesale account from you.

  2. 02

    Rive

    Sender is approved. Balance covers the destination rate. A route is chosen. Retryable errors try the next connector.

  3. 03

    Hand-off

    The message leaves on the connector for that country. You never pick it.

  4. 04

    Handset, then back

    The network delivers and reports. The receipt updates the ledger and is posted to your webhook.

A message travels from your product through Rive, which checks the sender, balance, and destination, hands it to a connector, and returns the delivery receipt to your ledger and webhook.
Messages
MessageToStatusSent
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
Product interface · example data

03 · Track

Every message keeps its trail.

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.

  • Status you can act on rather than a spinner.
  • Failure reasons recorded with the message.
  • The same record in the console, the API, and your webhook.

04 · Identity

Your name on the lock screen, reviewed first.

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 works
Senders
  • Acme Sign-in codes and receipts Approved
  • AcmeBooking Appointment reminders In review
  • TaxRefund Refused: reads as a public authority Not approved
Product interface · example names

05 · Spend

Prepaid, priced per destination.

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.

Billing

Available balance

$412.60

Illustration · example workspace

Spent, 30 days
$186.40
Messages, 30 days
4,210
Average
$0.0443
Top-ups
$600.00
  • Card top-up+$200.00
  • Message spend · Norway−$0.0440
  • Message spend · Sweden−$0.0510
Product interface · example figures

Destination rates

From the live price list, per accepted message.

All countries
  • NONorway from $0.0670
  • SESweden from $0.0760
  • DKDenmark from $0.0730
  • GBUnited Kingdom from $0.0640
  • USUnited States from $0.0445

06 · Operate

One console for the whole account.

Balance, traffic, senders, keys, webhooks, and support live together. No vendor dashboards, no spreadsheets of routes.

Open a workspace
Dashboard

Available balance

$412.60

Messages, 24h

2,418

Delivered

97.9%

Traffic, last 24 hours
Product interface · example data

07 · Use

Built for the messages that have to land.

Verify

Sign-in codes, two-factor, and password resets. Short, time-sensitive, and tracked per attempt.

Acme

Your Acme sign-in code is 482193. It expires in 5 minutes.

Alert

Security notices, delivery updates, and appointment changes, written for people.

Acme

A new sign-in to your Acme account from Oslo. Not you? Reset your password.

Notify

Opted-in product messages on the same infrastructure, with the same receipts.

Studio

Reminder: your session is tomorrow at 10:00. Reply STOP to opt out.

How Rive is run

Careful by default.

  • Sender reviewEvery sender name is checked before live traffic.
  • Hashed API keysKeys are shown once and stored only as a hash.
  • Abuse reports readReports go to a person at the compliance address.
  • Human supportTickets with a full history, not a chatbot.

Read the compliance overview, GDPR information, and live status.

Pricing

Pay for messages. Nothing else.

A standard account has no platform fee and no seats. Top up the balance; each accepted message costs its destination rate.

Platform fee
$0
Seats
None
Billing
Prepaid
Charged
Per accepted message

Questions

Straight answers.

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.

Send the first message today.

Create an account, request a sender, add funds, and call the API or send from the console.