API Keys

What a TestSprite API key is bound to, and how to create, expire, and revoke one.

How API Keys Work

An API key signs the CLI and the MCP Server in as you, inside one workspace. You mint it from that workspace’s API Keys page, and it is tied to your membership there: anything the CLI or MCP Server creates with it belongs to that workspace and draws on that workspace’s balance. To work in another workspace, mint a key there.

Keys are for Members and above; a Viewer is read-only and can’t hold one. A key stops working when you leave or are removed from the workspace, and none can be minted while the workspace is paused. You can have 2 active keys per workspace, so you can rotate one while the other stays in use — past that, revoke one first. Revoking is immediate.

Keys that start with sk-user- are from before workspace keys existed. They keep working, always act in your default workspace, and are listed on its API Keys page, where you can revoke them.

Creating a Key

Go to Workspace Settings → Connections → API Keys in the workspace the key should belong to and click New API Key.

Give it a descriptive name (e.g., “MCP Integration”) and pick an expiration: no expiry, or 30, 90, or 365 days. Without one the key doesn’t expire, unless the workspace enforces a maximum lifetime: then a longer expiry is rejected, and a key created without one gets that maximum. Click Create, then copy the key right away.

Store it securely. The full key is shown only once, at creation.

Managing API Keys

Field	Description
Name	Descriptive identifier
API Key	Only the leading characters (sk-member-abcdef…); the rest is never stored in a readable form
Last Used	When the key last authenticated a request
Created At	When generated
Expires	The expiration set at creation, or “Never”

Revoke disables a key immediately; requests using it are rejected. Members see and revoke their own keys; Admins and the Owner see every member’s keys in the workspace and can revoke any of them.

Viewing MCP Test Results

Projects created through the MCP Server in your IDE show up under All Projects > MCP.

Field	Description
Project Name	The project the MCP Server created
Source	Where the project was created (MCP here)
Status	Pass/fail/blocked counts from its latest results
Type	Frontend or Backend
Creator / Created At	Who created it, and when

Test Reports

Click a project to see its execution logs, per-test results, errors, and performance metrics.

View Example Test Report

A full example report, with execution logs and performance metrics

Next Steps

Workspaces

What a workspace is, plans, and pausing

CLI Quickstart

Use your key with the TestSprite CLI

MCP Server Installation

Use your key with the MCP Server

MCP Server Overview

The complete MCP Server guide