Rivet’s v1 API: documents, payments and treasury — and document writes where your environment has them enabled. Keys act as your organization and are managed by its admins in Settings — one OpenAPI contract, served by the build that answers it.
The normal Rivet sign-up. There is no separate developer account — API keys belong to your organization.
An organization admin names the key and picks its scopes. The secret is shown once; only its hash is kept.
Send the key as a bearer token. The key is your organization — there's no org id to pass.
curl https://api.rivet.network/v1/documents?type=invoice&limit=2 \
-H "Authorization: Bearer rk_live_Kq3Z…"Keys minted on staging start with rk_test_ and only work against the staging host. The full walkthrough — pagination, errors, rotation — is in the reference.
A key acts as your organization and only ever sees your own side of a connection — reads across documents, payments and treasury, plus document writes where your environment has them enabled. Every response carries the spec version it was produced under.
Invoices, bills, purchase orders, quotes and the rest — both directions, labelled the way your team sees them.
Payment context per document and the payment methods on file.
Your treasury accounts and their ledger-derived balances, for a verified organization.