Generate API Keys

Create and manage TestDino API keys to authenticate the Playwright reporter and upload test results from CI or local environments.

Every upload needs a valid key. This guide covers how to create, configure, and manage API keys for your TestDino project.

MCP Server uses a different authentication method. The MCP Server requires a Personal Access Token (PAT), not a Project API Key (See: TestDino PAT).

Create a Key

1. Open your project in TestDino
2. Go to Settings → API Keys
3. Click Generate Key
4. Enter a Name and Expiration period (1 to 365 days)
5. Click Create

The key is automatically copied to your clipboard. Store it in a password manager or your CI secrets. The key is shown once and cannot be retrieved later.

Use your API key

Node.js

Pass the key to the CLI with the --token flag:

npx tdpw upload ./playwright-report --token="your-api-key"

Or set it as an environment variable:

export TESTDINO_TOKEN="your-api-key"
npx tdpw upload ./playwright-report

Python

Pass the key to the CLI with the --token flag:

testdino upload ./test-results --token="your-api-key"

Or set it as an environment variable:

export TESTDINO_TOKEN="your-api-key"
testdino upload ./test-results

In CI workflows, store the key as a secret and reference it:

- name: Upload to TestDino
  run: npx tdpw upload ./playwright-report --token="${{ secrets.TESTDINO_TOKEN }}"

Set up CI/CD secrets

Never hardcode API keys in your workflow files. Store them as secrets and reference them at runtime.

GitHub Actions

1. Go to your repository → Settings → Secrets and variables → Actions
2. Click New repository secret
3. Name it TESTDINO_TOKEN
4. Paste your API key
5. Click Add secret

GitLab CI

1. Go to your project → Settings → CI/CD → Variables
2. Click Add variable
3. Set Key to TESTDINO_TOKEN
4. Paste your API key in Value
5. Check the Mask variable to hide it in logs
6. Click Add variable

Jenkins

1. Go to Manage Jenkins → Credentials
2. Select your domain (or global)
3. Click Add Credentials
4. Choose Secret text
5. Set ID to testdino-token
6. Paste your API key in Secret

Azure DevOps

1. Go to Pipelines → Library
2. Create or open a variable group
3. Add a variable named TESTDINO_TOKEN
4. Paste your API key
5. Click the lock icon to make it secret

CircleCI

1. Go to Project Settings → Environment Variables
2. Click Add Environment Variable
3. Name it TESTDINO_TOKEN
4. Paste your API key

Rotate a key

When a key expires or you suspect it’s been exposed:

1. Generate a new key in Settings → API Keys
2. Update your CI secrets with the new key
3. Run one upload to confirm the new key works
4. Revoke or delete the old key

Don’t delete the old key until you’ve confirmed the new one works. This avoids downtime if something goes wrong during the switch.

Security Practices

• Use short expiration periods for CI keys
• Create separate keys for different pipelines or environments
• Rotate keys if you suspect exposure
• Never commit keys to version control

Key Limits

Plan	Keys per project
Community	2
Pro	5
Team	10
Enterprise	Unlimited

Related

Getting Started

Initial setup and first upload

GitHub Actions

CI workflow setup

Node.js CLI

Full CLI reference

Project Settings

All project configuration