Skip to content

Platform

The parts of SMS you should not have to build.

Rive handles sender review, routing, pricing, receipts, and signed callbacks behind one API and one console.

How it runs

From your request to the handset, and back.

The same path whether you send from the API or the console.

  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.

For developers

Plain HTTP and JSON.

One endpoint to send, one to read status, and signed events when the network reports back. Store the key as RIVESMS_API_KEY.

API reference
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" }
}

In the product

What a workspace actually contains.

Send

Single and bulk sends from the API or the console, with the cost shown before the message leaves.

Routing by destination

Rive prices each message for its country and hands it to a connector for that route. Retryable errors try the next connector.

Messages ledger

Accepted, handed off, delivered, or failed with the reason, searchable by number and ID.

Sender review

Sender names are reviewed before live traffic. Impersonation of banks, authorities, and other brands is refused.

Signed webhooks

Sent, delivered, and failed events, signed with HMAC-SHA256. Verify with RIVESMS_WEBHOOK_SECRET.

API keys

Bearer keys stored as a hash, with per-minute rate limits, request logs, and instant revocation.

Prepaid billing

Card and crypto top-ups, a balance ledger, and the cost on every message row.

Abuse controls

Content checks before sending and an abuse address that reaches a person.

Support ledger

Tickets with the full conversation, answered by the operations team.