Generate TestDino API Keys

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 — test streaming, Public API calls, MCP, Azure DevOps — authenticates with a scoped credential. This guide shows how to create, rotate, and securely store the API Key for test reporting and the Personal Access Token (PAT) for Public API and MCP access. The API key is the first step of setup. Create it here, then integrate TestDino with the Node.js CLI to stream results from your machine, or wire it into CI to stream on every run. For first-time setup, create an API Key (test reporting) — the Personal Access Token is only for the Public API and MCP.

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. Pick the one that matches what you’re doing:

Credential	Use it for	Where you create it
API Key	Streaming Playwright test results	Project Settings → API Keys
Personal Access Token (PAT)	Public API and MCP access	User Settings → Personal Access Tokens

The API Key lives on the project. Open the project first, then go to Project Settings → API Keys tab → Keys & Tokens section. The PAT is a user credential you create from User Settings → Personal Access Tokens. Each credential is shown only once at creation.

Project vs User settingsThe API Key belongs to a single project (Project Settings). The PAT belongs to you as a user (User Settings) and can reach any project you have access to. 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.

Prefix	Token type	Scope	Accepted by
`td_pat_`	Personal Access Token (PAT)	User (access to your projects)	Public API v1 and MCP
`td_api_`	Project API Key	Project-scoped	Streaming/CI uploads, Azure DevOps Extension (`azureext`)

Public API and MCP requests use a td_pat_ PAT in the header: Authorization: Bearer td_pat_.... Create it from User Settings → Personal Access Tokens with the public-api scope. The td_api_ Project API Key is used for streaming test results and the Azure DevOps Extension.

API Key (test reporting)

Use this to stream Playwright test results to TestDino. It has the td_api_ prefix.

Open your project in TestDino
Go to Project Settings → API Keys tab
In the Keys & Tokens section, click + New → API Key
Enter a Key Name and Expiration (1 to 365 days)
Click Create API Key

Create API Key modal showing Key Name and Expiration in days fields

Personal Access Token (Public API & MCP)

Use this for the Public API and the MCP integration. It is a user credential that reaches any project you have access to.

Sign in to TestDino, open your profile, then User Settings
Go to Personal Access Tokens and click Generate new token
Enter a Token Name and select the public-api scope
Grant access to the projects you need, set an Expiration, and create it

The td_pat_ token is shown once, so copy it right away. Store it in a password manager or your CI secrets.

Access Token (Azure DevOps Extension)

TestDino Keys & Tokens page with the New dropdown expanded showing API Key and Access Token options

Use this for the Azure DevOps Extension. It is a project-scoped td_api_ token (the same key type used for streaming), created with the azureext scope.

Open your project in TestDino
Go to Project Settings → API Keys tab
In the Keys & Tokens section, click + New → Access Token
Enter a Token Name, select the azureext scope, set Expiration (days), and click Create Token

The credential is copied to your clipboard and shown once. Keys & Tokens table listing API Key and Access Token rows with Name, Type, Status, Scopes, Created At, and Expires At columns

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

@testdino/playwright reads the key from the TESTDINO_TOKEN environment variable. Set it, then run your tests. Results stream to TestDino during the run:

export TESTDINO_TOKEN="your-api-key"
npx playwright test

The key is referenced once in your Playwright config, so every run picks it up:

playwright.config.ts

import { defineConfig } from '@playwright/test';

export default defineConfig({
  reporter: [
    ['@testdino/playwright', { token: process.env.TESTDINO_TOKEN, serverUrl: "https://reporter.testdino.com" }],
  ],
});

In CI workflows, store the key as a secret and expose it to the test step:

- name: Run Playwright tests
  env:
    TESTDINO_TOKEN: ${{ secrets.TESTDINO_TOKEN }}
  run: npx playwright test

Set up CI/CD secrets

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

GitHub Actions
GitLab CI
Jenkins
Azure DevOps
CircleCI

Go to your repository → Settings → Secrets and variables → Actions
Click New repository secret
Name it TESTDINO_TOKEN
Paste your API key
Click Add secret

Go to your project → Settings → CI/CD → Variables
Click Add variable
Set Key to TESTDINO_TOKEN
Paste your API key in Value
Check the Mask variable to hide it in logs
Click Add variable

Go to Manage Jenkins → Credentials
Select your domain (or global)
Click Add Credentials
Choose Secret text
Set ID to testdino-token
Paste your API key in Secret

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

Go to Project Settings → Environment Variables
Click Add Environment Variable
Name it TESTDINO_TOKEN
Paste your API key

Rotate a key

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

Generate a new key in Project Settings → API Keys tab
Update your CI secrets with the new key
Run one upload to confirm the new key works
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

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

Next steps

With a key in hand, integrate TestDino to stream results from your machine, or set up CI to stream on every run.

Node.js CLI

Install @testdino/playwright and stream your first run

CI Setup

Stream results 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

Getting Started

Installation & Setup

AI & Automation

Debug & Analyze

Optimize CI

Test Management

Integrations

Administration

Create a Key

Token prefixes

API Key (test reporting)

Personal Access Token (Public API & MCP)

Access Token (Azure DevOps Extension)

Use your API key

Set up CI/CD secrets

Rotate a key

Security Practices

Key Limits

Next steps

Node.js CLI

CI Setup

Public API

Project Settings

​Create a Key

​Token prefixes

​API Key (test reporting)

​Personal Access Token (Public API & MCP)

​Access Token (Azure DevOps Extension)

​Use your API key

​Set up CI/CD secrets

​Rotate a key

​Security Practices

​Key Limits

​Next steps

Node.js CLI

CI Setup

Public API

Project Settings

Create a Key

Token prefixes

API Key (test reporting)

Personal Access Token (Public API & MCP)

Access Token (Azure DevOps Extension)

Use your API key

Set up CI/CD secrets

Rotate a key

Security Practices

Key Limits

Next steps