Developers

Your organization’s documents and payments, over one API.

Rivet’s v1 API: documents and payments today, treasury coming — 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.

Illustrative. The full walkthrough is in the reference.

Quickstart

Three steps to your first page of documents.

  1. Step 1

    Create an account

    The normal Rivet sign-up. There is no separate developer account — API keys belong to your organization.

  2. Step 2

    Mint a key in Settings → Developers

    An organization admin names the key and picks its scopes. The secret is shown once; only its hash is kept.

  3. Step 3

    Make your first request

    Send the key as a bearer token. The key is your organization — there's no org id to pass.

First request · spec v1.30.0
curl https://api.rivet.network/v1/documents?type=invoice&limit=2 \
  -H "Authorization: Bearer rk_live_Kq3Z…"

A key’s prefix follows its organization: rk_live_ for a live one, rk_test_ for a sandbox. The full walkthrough — pagination, errors, rotation — is in the reference.

What’s in v1

Org-scoped, one contract.

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.

Available

Documents

Invoices, bills, purchase orders, quotes and the rest — both directions, labelled the way your team sees them.

Available

Payments

Payment context per document and the payment methods on file.

Coming

Treasury

Your treasury accounts and their ledger-derived balances, once Rivet Money is available to you.

For agents

Give your own agent the same context.

The Rivet MCP server runs beside your agent and turns the contract into MCP tools, one per operation, acting as your organization with the scopes of the key you give it.

See the Context API
$ npx -y @rivet-network/mcp
# tools
listDocuments · getDocument · transitionDocument · payDocument …
Developers

Start with an account. Keys come with it.

There is no separate developer account. API keys belong to your organization.