Skip to main content
What you’ll learn
  • How to generate and configure API keys
  • How to rotate and revoke keys securely
  • How to store keys as CI secrets
Every TestDino integration — CLI uploads, Public API calls, Azure DevOps — authenticates with a scoped credential. This guide shows how to create, rotate, and securely store API Keys for test reporting and Access Tokens for Public API access and external integrations. The API key is the first step of setup. Create it here, then install a reporter to upload from your machine or wire it into CI to upload on every run. For first-time setup, create an API Key (test reporting) — the Access Token is only for the Public API and external integrations.

​
Create a Key

Create Project Access Token modal showing Token Name, Scopes (azureext, public-api), and Expiration in days fields TestDino issues two credential types from the same place. Pick the one that matches what you’re doing:
CredentialUse it forWhere it’s used
API KeyUploading Playwright test resultsCLI uploads (Node.js / Python), CI pipelines
Access TokenPublic API access and external integrationsPublic API v1, Azure DevOps Extension
Both live on the project — not the organization. Open the project first, then go to Project Settings → API Keys tab → Keys & Tokens section. Each credential is shown only once at creation.
Project vs Organization settingsOrganizations have their own Settings page (billing, members, etc.), but API keys and Access Tokens always belong to a single project. If you don’t see the API Keys tab, you’re likely in Org Settings — navigate into a project first.

​
Token prefixes

Every credential carries a prefix that identifies its type. Check the prefix to confirm you are using the right token for the surface.
PrefixToken typeScopeAccepted by
tdp_Project Access TokenProject-scoped (public-api, azureext)Public API v1, Azure DevOps Extension, CLI uploads
tpu_User Access TokenUser-scopedMCP and in-app contexts. Rejected by Public API v1
Public API requests must use a tdp_ token in the header: Authorization: Bearer tdp_.... A tpu_ token returns an authorization error on Public API v1. User tokens are created from your user settings and are used by the MCP integration, not from the project API Keys tab.

​
API Key (test reporting)

Use this for the CLI uploaders that send Playwright reports to TestDino.
  1. Open your project in TestDino
  2. Go to Project Settings → API Keys tab
  3. In the Keys & Tokens section, click + New → API Key
  4. Enter a Key Name and Expiration (1 to 365 days)
  5. Click Create API Key
Create API Key modal showing Key Name and Expiration in days fields

​
Access Token (Public API & integrations)

TestDino Keys & Tokens page with the New dropdown expanded showing API Key and Access Token options Use this for the Public API or external integrations like the Azure DevOps Extension.
  1. Open your project in TestDino
  2. Go to Project Settings → API Keys tab
  3. In the Keys & Tokens section, click + New → Access Token
  4. Enter a Token Name
  5. Select Scopes — public-api for Public API v1 read-only access, azureext for the Azure DevOps Extension
  6. Set Expiration (days) (1 to 365 days)
  7. Click Create Token
The credential is automatically copied to your clipboard. Store it in a password manager or your CI secrets — it’s shown once and cannot be retrieved later. Keys & Tokens table listing API Key and Access Token rows with Name, Type, Status, Scopes, Created At, and Expires At columns

​
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 Project Settings → API Keys tab
  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
TipDon’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

PlanKeys per project
Community2
Pro5
Team10
EnterpriseUnlimited

​
Next steps

With a key in hand, install a reporter to upload from your machine, or set up CI to upload on every run.

Reporters

Install the Node.js or Python CLI and run your first upload

CI Setup

Automate uploads in GitHub, GitLab, Azure DevOps, and more

Public API

Use an Access Token to query test data over the API

Project Settings

All project configuration