What you’ll learn
- How to generate a Project PAT with the
public-apiscope - How to make an authenticated request with curl, Node.js, and Python
- How to verify your setup before calling data endpoints
Prerequisites
- A TestDino account with at least one project (sign up)
- Admin access on the project where you’ll generate the token
Steps
Generate a Project PAT
- Open your project in TestDino
- Go to Project Settings → API Keys tab
- In Keys & Tokens, click + New → Access Token
- Name it, select the
public-apiscope, set an expiration, and click Create Token
tdp_ token is auto-copied — save it, shown only once.Full workflow: Generate API keys.Get ProjectID
- Open the project in the TestDino App
- Copy the
project_...segment from the URL
.../projects/project_69e1bb123.../test-runsVerify the token
Call A
/token-info to confirm the token is valid and scoped correctly:- curl
- Node.js
- Python
200 OK response with success: true confirms the setup is working.Troubleshooting
401 AUTH_INVALID_TOKEN
401 AUTH_INVALID_TOKEN
The token is missing, malformed, expired, or revoked. Check:
- Header is
Authorization: Bearer tdp_...(case-sensitive, single space) - The token starts with
tdp_(Project PAT, not a user token) - The token hasn’t been rotated or revoked in Project Settings
403 Forbidden
403 Forbidden
The token is valid but doesn’t belong to the
projectId in the URL. Project PATs are scoped to one project — use the PAT that matches.429 RATE_LIMIT_EXCEEDED
429 RATE_LIMIT_EXCEEDED
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.