professional plan

Programmatic API Keys

Scoped, rotatable keys for automation and integrations.

What It Does

Programmatic API Keys let machines use the platform safely. Instead of embedding a person's login in a script, you issue a dedicated key with the scopes the automation should have, and those scopes can never exceed what the key's creator is allowed to do. The same key powers the CI/CD integrations and the MCP server for AI agents. Each key shows when it was last used, so stale keys are easy to spot, and rotation issues a new key while the old one keeps working for a grace window you choose, up to 30 days. This is the foundation for integrating the platform into CI/CD, internal dashboards and any tooling that needs to trigger tests or read results without a browser.

Programmatic API keys: a ci-pipeline key scoped to running packs, never more than its creator may do, is created, a second key can be rotated or revoked and an old key shows as revoked; the key is stored as a CI secret and the pipeline uses it to start a test pack run through the Shift-Left REST API and read back the results

Overview

Generate API keys to drive the platform programmatically: trigger test packs, poll their status, pull results, connect AI agents through the MCP server, and wire the platform into your own tooling. A key's scopes come from the same permission catalogue as roles, and a key can never exceed the permissions of the person who created it. Keys are shown once and stored only as a SHA-256 hash, can carry an expiry, can be revoked instantly, and can be rotated with a grace window of up to 30 days so pipelines switch over without downtime.

Key Capabilities

Scopes from the same permission catalogue as roles
Key scopes are capped by the creator’s role permissions
Shown once, stored as a SHA-256 hash, with optional expiry
Rotate with a grace window of up to 30 days, or revoke instantly
Drive the public REST API, CI integrations and the MCP server
Platform-wide per-IP rate limiting; last-used time shown per key

How It Works

  1. 1

    Create an API key and assign its scopes

  2. 2

    Copy the key once and store it securely in your automation or pipeline

  3. 3

    Call the public REST API to trigger runs and read results

  4. 4

    Check each key’s last-used time, and rotate with a grace window when needed

  5. 5

    Revoke a key immediately if it is no longer needed

Available on

professional Plan & Above

Upgrade to the professional plan to unlock this feature.

Available on Professional plan and above
See pricing →

Go deeper

Guides and playbooks that show this capability in practice.

Try API Keys Today

Start your 15-day free trial — no credit card required.