The account API handles identity, consent and operational metadata. There is no endpoint for financial records or SMS.
App integrations
Use Rivu’s local CSV import/export, encrypted portable backups and
confirmation-based rivu://add links. Shared links open an
editor; they cannot silently save an entry or read the ledger. Treat
readable exports as a deliberate disclosure.
Account API
REST API v1: /api/v1. Web uses HttpOnly session cookies with
CSRF protection. Mobile uses an opaque bearer session stored in the
device’s encrypted account store. Never embed API secrets in an app.
Endpoints cover authentication, sessions, account export/deletion, consent and fixed-schema product events. The downloadable OpenAPI contract describes the current endpoints. Dev, staging and UAT also expose the live schema at /api/openapi.json.
AI providers
Bring your own provider key inside the app. Rivu’s account backend never receives it. The Android app runs compatible GGUF models on the CPU. iPhone local inference is not yet implemented.
Authentication
Native clients use an opaque bearer session. Browser clients use an HttpOnly session cookie and the X-Rivu-CSRF header for changes. Administrators need a recent authenticator step-up. Account exports are paginated; follow the returned cursor and snapshot until next is null.
Telemetry
Ingestion accepts fixed screen/action identifiers only, with current account consent. Unknown fields, transaction values, message text and arbitrary labels are rejected. Repeated event IDs are safe to retry. This API cannot read or synchronize a device ledger.