Skip to main content
The TestDino Public API uses personal access tokens (PATs) for authentication. Every request sends the token as a Bearer header. This quickstart walks through generating a token, verifying it, and calling your first data endpoint.

Prerequisites

  • A TestDino account with at least one project (sign up)
  • Access to a project the PAT can read

Steps

1

Generate a PAT

  • Sign in to TestDino, open your profile, then User Settings
  • Go to Personal Access Tokens and Generate new token
  • Name it, select the organizations and projects it may access, pick an expiration of 30, 60, 90, or 180 days, and create it
The td_pat_ token is shown once, so copy it right away.Full workflow: Generate API keys.
2

Get ProjectID

  • Open the project in the TestDino App
  • Copy the project_... segment from the URL
Eg: .../projects/project_69e1bb123.../test-runs
TipFor CI/CD or automation, export TESTDINO_API_TOKEN and TESTDINO_PROJECT_ID as env vars, and keep the token as a secret.
3

Verify the token

Call /token-info to confirm the token is valid and scoped correctly:
A 200 OK response with success: true confirms the setup is working.
4

Call a data endpoint

List the 5 most recent test runs:

Troubleshooting

The header is missing, the token does not start with td_pat_, or the token is not recognized. Check:
  • Header is Authorization: Bearer td_pat_... (case-sensitive, single space)
  • The token starts with td_pat_
  • The token has not been rotated or deleted in User Settings
The token was revoked, or it passed its expiry date. Generate a new PAT in User Settings → Personal Access Tokens and update your stored secret.
The resource does not exist, or the token does not cover the projectId in the URL. Use a PAT that was granted access to that project.
You’ve hit the 100 requests/minute per-token limit. Wait for the RateLimit-Reset timestamp in the response headers, or implement exponential backoff. See Rate limits.