Skip to main content
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. API Keys management interface showing key list and generate button

​
Use your API key

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
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.
  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

​
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.

​
Who can manage keys

API key management requires project-level permissions:
RoleCan create keysCan revoke keysCan view keys
Admin✓✓✓
Editor✓✓✓
Viewer✗✗✓
See Permissions for full role details.

​
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

PlanKeys per project
Community2
Pro5
Team10
EnterpriseUnlimited

Getting Started

Initial setup and first upload

GitHub Actions

CI workflow setup

Node.js CLI

Full CLI reference

Project Settings

All project configuration
Need help? Reach out on Discord or email [email protected].