Skip to main content
The TestDino developer portal is the entry point for programmatic access: the REST API, the machine-readable OpenAPI specification, the MCP server for AI agents, and the credentials each one needs.

Quick Reference

Machine-readable endpoints

Agents and code generators can fetch these directly. No authentication is required to read them. Every operation in the specification carries a unique operationId, a description, typed parameters, and a response schema, so it converts directly into LLM function-calling definitions.

Authenticate

TestDino has 2 authentication paths. Which one you use depends on the surface you call. The REST API uses a personal access token sent as a Bearer token on every request.
Create a PAT from User Settings → Personal Access Tokens, granting it access to the specific organizations and projects it may read. Full workflow: Generate API keys.

OAuth 2.0 for the remote MCP server

The remote MCP server at https://mcp.testdino.com authenticates over OAuth 2.0. An agent that supports remote MCP discovers the endpoints from standard metadata, so no manual token handling is needed. The server supports the authorization_code grant with S256 PKCE, dynamic client registration, and the mcp scope. The local MCP server uses a PAT from the TESTDINO_PAT environment variable instead.

Error handling

Every error returns JSON with a stable error.code, an HTTP status, and a human-readable message. Branch on error.code, not on status alone.
The full code table, retry guidance, and rate-limit headers are in API standards.

Rate limits

Authenticated responses carry RateLimit-Limit, RateLimit-Remaining, and RateLimit-Reset; requests rejected before authentication do not. Back off on 429 and 5xx only.

API Reference

Every endpoint, grouped by resource.

MCP Server

Connect an AI agent to live test data.

Generate API Keys

Create and scope a td_pat_ token.