API Keys

Personal Access Tokens (PATs) allow you to authenticate with the TestKase API programmatically — for CI/CD pipelines, test automation, and integrations.

Creating a Token

1. Go to Profile → API Keys (or testkase.com/api-keys)
2. Click Create Token
3. Give it a descriptive name (e.g., "CI/CD Pipeline")
4. Copy the token — it's only shown once

Token Format

PATs start with xyz_ prefix:

xyz_abc123def456...

Using Tokens

In API Calls

curl -H "Authorization: Bearer xyz_your_token_here" \
  https://api.testkase.com/api/v1/projects/user/my-projects

In Test Frameworks

Pass the token as an environment variable to the TestKase reporter:

TESTKASE_API_KEY=xyz_your_token_here npx testkase-reporter

In CI/CD

Store the token as a secret in your CI/CD platform and reference it in your pipeline config.

Token Security

• Tokens have the same permissions as the user who created them
• Maximum 10 tokens per user
• Tokens do not expire automatically — revoke them when no longer needed
• Never commit tokens to source code — use environment variables

Revoking Tokens

1. Go to API Keys page
2. Click the revoke icon next to the token
3. The token is immediately invalidated

PAT vs Cookie Authentication

All three methods are supported simultaneously. The backend checks Authorization header first, then falls back to cookie.