Environments & API keys

Renduo separates API keys into environments so you can keep production and test traffic apart. A key belongs to exactly one environment, and every request authenticates with exactly one key.

What an environment is

An environment is a named partition of your organization — production, staging, development, or a custom name. Your first login automatically creates a production environment, so there is no setup step. You can have several environments per organization, and each one has its own keys.

The API key format

Keys look like this:

rnd_live_3f8a2c…       # production environment
rnd_test_7b1e9d…       # test environment

The live/test prefix tells you which environment the key belongs to. Keys are sent on every request as a Bearer token:

Authorization: Bearer rnd_live_3f8a2c…

Scopes

A key is created with a set of scopes that limit what it can do — a least-privilege key does not need every scope:

Scope	Unlocks
`generate`	Generate PDFs.
`templates:read`	List templates and assets.
`templates:write`	Register templates and upload/delete assets.
`generations:read`	Poll async job status.
`admin`	Full access.

Key lifecycle

Creation: keys are created in the dashboard (there is no public endpoint to mint a key). You choose the environment and scopes.
Revealed once: the full key is shown a single time at creation, in the form rnd_live_… (or rnd_test_…). Copy it immediately.
Revocation: revoking a key from the dashboard invalidates it for all future requests. Create a new one to replace it.
Rotation: create a new key, switch your client to it, then revoke the old one.

Managing environments & keys

From the dashboard you can create, rename, and delete environments (deleting carries a cascade warning: keys and data under that environment go with it), and create/revoke keys within each environment.