Skip to main content
The Testorim HTTP API lets a pipeline, a terminal or an integration start test runs and read their results.

Authentication and API keys

Mint a key, send it, and understand what it can reach.

Base URL

Every route mounts flat under /api. There is no version prefix.

Authentication

An HTTP Bearer token on the Authorization header:
A key is pinned to one workspace. Resources in another workspace return 404, not 403.

Starting a run

The response is 202 Accepted with a run id. Poll GET /api/runs/{id} until the status is terminal, then read overallStatus for the verdict. Ad-hoc runs take a projectId and a description instead of a procedureId.

Errors

Scope

This reference documents the API-key surface. The app itself calls many more endpoints: billing, provider webhooks, OAuth callbacks, fixtures, environments, schedules, alerts, visual baselines, sharing, flakiness, variables, performance budgets, role probes, workspace management. Those are session-oriented or provider-signed and are deliberately not published as an integration surface. Testorim does not send outbound webhooks.