HTTP API v1
Use Autonomy's 23 operations from scripts, CI jobs and other HTTP clients.
The HTTP API v1 lets scripts, CI jobs and services work with Autonomy directly. It covers projects, test cases, test plans, runs (with their Step Actions and evidence), environments and issues.
The base URL is https://api.autonomyqa.com. Every operation uses the same route shape and a JSON object body:
POST https://api.autonomyqa.com/api/v1/<resource>.<verb>
Authorization: Bearer <credential>
Content-Type: application/jsonFor example, test_case.create is POST /api/v1/test_case.create and run.get is POST /api/v1/run.get. There is no query string: every argument goes in the body, even for reads. A successful response is the operation's result as JSON, with no wrapper.
The machine-readable OpenAPI 3.1 document is at GET /api/openapi.json. Each operation's operationId is its name with the dot replaced by an underscore, such as test_case_create, and x-scope names the scope it needs.
Operations at a glance
| Resource | Operations |
|---|---|
| Projects | project.list, project.get |
| Test cases | test_case.list, test_case.get, test_case.create, test_case.update_steps, test_case.archive |
| Test plans | test_plan.list, test_plan.get, test_plan.create, test_plan.set_members |
| Runs | run.trigger, run.list, run.get, run.step_actions, run.evidence |
| Environments | environment.list, environment.get, environment.upsert |
| Issues | issue.list, issue.create, issue.comment, issue.set_status |
Creating a test case, a test plan or an environment needs a projectId, and list operations can filter by one. Call project.list first to find it.
HTTP API and MCP
HTTP and MCP share the same 23 operations, with the same arguments, results, scopes, confirmation rules and errors. On MCP, each operation is a tool named autonomy_ plus the operation name with dots replaced by underscores, such as autonomy_run_get.
Use MCP when an AI assistant should work with Autonomy from an editor. Use this HTTP API for scripts, CI pipelines and systems that send JSON requests. The two differ in how you sign in: the HTTP API accepts organization API keys and OAuth tokens, while MCP uses OAuth only.
Start here
- Authenticate each request.
- Pick an operation from the operation catalog.
- Follow runs and read their evidence with the runs and evidence workflow.
- Handle the errors.
Didn’t find it?