Skip to main content
Interfere uses public app keys for telemetry and secret API keys for authenticated operations. Secret keys have explicit scopes and an expiration setting. Keep them in your secret manager or CI environment.

App keys

Open an app and copy its Public key from the sidebar. Use the public key in the SDK to capture telemetry. It is safe to include in browser code. Use the app’s secret key with release:write to register releases and upload source maps. Interfere shows the secret key once, when you create the app; to issue a new one, run Reroll INTERFERE_API_KEY from the app’s command menu. Set INTERFERE_API_KEY in the build environment for SDK plugins. The CLI uses INTERFERE_SECRET_KEY for secret key authentication.

Workspace keys

Use a workspace API key for unattended workspace operations, including Terraform. Its scopes determine which resources it can read or change. For interactive work, sign in through MCP or the CLI. OAuth uses your existing workspace permissions. For native OpenTelemetry ingestion, use a workspace key with Send telemetry (org:telemetry:write). See OpenTelemetry ingestion for setup and exporter configuration.

Create a workspace key

Install the CLI, then sign in through your browser:
Use an Owner or Admin account with permission to manage workspace authentication. You can only grant permissions your account already has. Create a key for Terraform to manage apps, which the API and scopes call surfaces. Replace acme with the workspace slug from your Interfere URL, and replace the example UUID with a new UUID:
The response contains apiKey.id, apiKey.name, and apiKey.secret. Save the ID for revocation and store the secret in your secret manager. Configure your CI environment to supply that secret as INTERFERE_TOKEN when it runs Terraform. This key expires after 30 days. Set the lifetime to the number of seconds your automation needs. Keep the same UUID and arguments if you retry an uncertain creation request; use a new UUID for a different key. The example grants app management only. To manage workspace settings or issue additional keys, add the permissions listed for those Terraform resources. You can inspect all accepted fields with interfere keys private create --schema.

Permission changes

A workspace key’s access is limited to its explicit scopes and its creator’s current workspace permissions. Removing the creator’s membership removes the key’s management access. A key does not grant permissions its creator lacks.

Revoke a key

Create a replacement and update the automation that uses the old key. Then revoke the old key using its saved ID:
Revocation prevents subsequent requests from using that credential. For app credentials, open the app. Public ingestion credentials and secret build credentials serve different purposes; copy the credential required by your SDK or tool.