Manage API keys

API keys (rpk_...) authenticate CLI and programmatic access to Repster Cloud. Keys are org-scoped and can be created, listed, and revoked.

List keys

rp keys list
rp keys list --profile prod

Shows key prefix, name, status, last-used date, and creation date. Key values are never shown after creation.

Create a key

rp keys create
rp keys create --name "ci-deploy-key"

The raw key is printed once; copy it immediately. It cannot be retrieved again.

Revoke a key

rp keys revoke <key-id-or-prefix>
rp keys revoke rpk_abc123 --yes    # skip confirmation prompt

Revoked keys are rejected immediately by Repster Cloud.

Using keys in CI

Set the key as an environment variable; repster picks it up automatically:

REPSTER_API_TOKEN=rpk_... rp deploy

Or configure it in a named profile:

rp login --token rpk_... --profile ci

Then use --profile ci in commands that need it.

Key roles

Creating, listing, and revoking API keys requires the org admin role. A key authenticates as the user who created it and inherits that user's current role in the org (see the role table in Manage your team).

Web UI

Keys can also be created and revoked in the Repster Cloud UI (repster.online) under Settings → API Keys.