Skip to main content

Blastoff workspace API keys

Workspace API keys connect the Testronaut CLI to one Blastoff workspace. Reports, screenshots, MFA configurations, and hosted inbox lookups performed through that CLI session use the workspace's shared resources rather than your personal workspace.

Create a key​

  1. Sign in to Mission Control.
  2. Select the Blastoff workspace from the workspace selector.
  3. Open Workspace.
  4. Under Your workspace API keys, select Create workspace API key.
  5. Copy the complete tn_... value immediately. Only its prefix is shown later.

Treat the key as a password. Do not commit it, paste it into mission files, or share it in chat or issue trackers. Each member should create and manage their own key.

Use it with the CLI​

From the project whose reports should belong to the workspace, run:

testronaut login

Login exchanges the API key for a short-lived session token and stores that token in the project's testronaut-config.json. Subsequent commands use the workspace scope:

testronaut upload
testronaut missions/login.mission.js

The selected scope comes from the key, not from the workspace currently selected in the browser. Run testronaut login again with a personal key to return that project to personal uploads, or with another workspace key to change its destination.

Verify the destination​

After uploading a report:

  1. Select the Blastoff workspace in Mission Control.
  2. Open the dashboard and locate the report.
  3. Switch to Personal and confirm the workspace report is not present there.

Revoke a key​

In Workspace → Your workspace API keys, delete the key. Deletion immediately revokes it; existing CLI session tokens derived from it are rejected on their next API request. Sign in again with another key to continue.

Removing a member also removes workspace access. Keys are bound to both their creator and organization, so they cannot be reused for a different workspace.

Troubleshooting​

  • Invalid API key: confirm the app and API target the same environment and database.
  • API key has been revoked: create a replacement key and run testronaut login again.
  • Workspace access is no longer available: ask an Owner or Admin to confirm membership.
  • Workspace is read-only: an Owner must resolve the workspace subscription status.
  • Report appears under Personal: the project still contains a session minted from a personal key; log in again using the workspace key.