Generate TestDino API Keys

Create a project API key to stream Playwright test results to TestDino. Use a Personal Access Token (PAT) only for the Public API and MCP.

Credential	Use for	Create in	Prefix
API Key	Streaming test results, CI uploads	Project Settings → API Keys	`td_api_`
Personal Access Token (PAT)	Public API and MCP	User Settings → Access Tokens	`td_pat_`

If you don’t see the API Keys tab, open a project first. Org Settings has no API Keys tab. Creating or deleting a project API key requires the Owner or Admin role in the organization.

Set up with an AI agent

Paste this into Cursor, Claude Code, or another assistant after you have created a key in the UI:

Wire a TestDino API key into Playwright and CI as TESTDINO_TOKEN.

Open in Cursor

First-time project setup with the full agent prompt: Getting Started. MCP and PAT flows: AI Onboarding.

Create an API key

Open your project in TestDino
Go to Project Settings → API Keys
Click Generate New Key
Enter a Name, pick a Type (Ingestion for local or CI uploads, Pipeline for Azure DevOps and TeamCity plugins), and choose an Expiry of 30, 60, 90, or 180 days
Click Generate Key

The key is shown once. Copy it and store it as TESTDINO_TOKEN.

Use the key

Reference the env var in Playwright config:

playwright.config.ts

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

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

Set TESTDINO_TOKEN, then run your tests. Results stream during the run:

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

Store the key in CI

Never hardcode API keys in workflow files. Store them as secrets and expose TESTDINO_TOKEN to the test step. Full pipeline configs are in CI Setup.

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

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

Go to your project → Settings → CI/CD → Variables
Click Add variable
Set Key to TESTDINO_TOKEN
Paste your API key in Value
Check 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

Create a Personal Access Token

Use a PAT for the Public API and MCP. It is a user credential that reaches the organizations and projects you select at creation.

Open your profile menu → Access Tokens
Click Generate New Token
Enter a Token Name, choose an Expiration, and select at least 1 project under Projects this token can access
Click Generate Token

The td_pat_ token is shown once. Use it as Authorization: Bearer td_pat_....

Prefer short expirations for CI. Use separate keys per pipeline or environment. Never commit keys to version control. When a key expires or is exposed, create a new key, update your secret, then delete the old one. Deleting a key stops anything still using it immediately and cannot be undone.

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 a PAT to read and act on test data over the API

Project Settings

All project configuration

Getting Started

Connect Your Pipeline

Test Intelligence

Guides

AI-Native Testing

Organization & Access

Integrations

Test Management

Data Security & Privacy

Resources

Set up with an AI agent

Create an API key

Use the key

Store the key in CI

Create a Personal Access Token

Node.js CLI

CI Setup

Public API

Project Settings

​Set up with an AI agent

​Create an API key

​Use the key

​Store the key in CI

​Create a Personal Access Token

Node.js CLI

CI Setup

Public API

Project Settings

Set up with an AI agent

Create an API key

Use the key

Store the key in CI

Create a Personal Access Token