CLI & API Keys
Create and manage the tvb_… API keys used by the testvibe CLI, MCP and AI tools, the tunnel agent, and the load telemetry agent.
Last updated
Was this helpful?
Create and manage the tvb_… API keys used by the testvibe CLI, MCP and AI tools, the tunnel agent, and the load telemetry agent.
TestVibe API keys — they start with tvb_ — authenticate tools that talk to TestVibe from outside the app. Manage them in Settings → CLI & API keys.
testvibe CLI
Work with projects, tests, and runs from the terminal.
MCP and AI tools
Let AI assistants call the TestVibe API on your behalf.
tvtunnel agent
Connects a device so cloud runs can reach private apps.
Load telemetry agent
Streams server metrics into load test results.
Open Settings.
Select CLI & API keys.
Create a new key and give it a descriptive name — one key per tool or machine keeps revocation painless.
Copy the key and store it somewhere safe. Treat it like a password.
Revoke a key from the same panel when a machine is retired or a key may have leaked.
The CLI & API keys panel also shows the install commands for the testvibe CLI. The simplest is npm (Node 20+):
npm install -g testvibeNo npm? The panel's fallback commands download a single dependency-free file from your TestVibe server and add a testvibe command to ~/.testvibe/bin:
Then sign in with a key from this panel and pick a project:
API keys authenticate tools against TestVibe. Values your tests need — logins, tokens, test data — belong in Settings → Variables & Secrets and are referenced from Gherkin as {{var:NAME}} / {{secret:NAME}}. See Add API keys and secrets.
REST API reference — the full API your keys authenticate against.
Last updated
Was this helpful?
Was this helpful?
# macOS / Linux (Node 20+)
curl -fsSL <your-testvibe-url>/api/v1/install.sh | sh# Windows PowerShell (Node 20+)
iwr -useb <your-testvibe-url>/api/v1/install.ps1 | iextestvibe login --server <your-testvibe-url> --key tvb_…
testvibe use <project>