List projects in the QA Touch domain. Paginated (50 per page); the response includes pagination metadata (current_page, last_page, total). Pass page to fetch subsequent pages.

Get a single project's detail including test case, test run, defect and milestone (release) counts.

Create a new project in the QA Touch domain.

List test cases for a project. Paginated (50 per page). Optionally filter by ONE of: approvalstatus, moduleKey, mode, or requirementKey — the QA Touch API rejects multiple filters in one request. view: "count" (only valid together with mode) returns just the count.

Get a single test case's detail: mapped test runs with status, custom field values, and step descriptions with expected results.

List the steps (description + expected result) of a test case. Works for both test cases and test run cases; step result keys returned here are used for step-level status updates.

List the modules (sections) of a project. Set includeCounts to also return the hierarchical module/submodule test case counts.

Create a new module (section) for test cases in a project. Pass parentKey to create it as a child of an existing module.

Create a test case in a module (section). template selects the style:

• exploratory: no predefined steps

• text: single steps text + expected_result

• bdd: Gherkin feature script (featureScript required)

• steps: structured step list (stepsTemplate required)

Update an existing test case. template must match the case style: exploratory, bdd (featureScript required) or steps (stepsTemplate required). Only provided fields are sent.

Bulk import test cases into a project from a local CSV file (QA Touch sample format). Max 100 test cases per request; file max 2 MB.

List the releases (milestones) of a project.

Create a new release (milestone) in a project.

List the test plans of a project, optionally filtered by name.

List the workspaces (groups/teams) of the QA Touch domain.

List the test runs of a project, optionally filtered by name.

Get a single test run's detail.

List test run results. source selects the lookup:

• run: all results of a test run (requires projectKey + testRunKey; paginated, 100 per page)

• release: results for a release (requires projectKey + releaseKey; optional status filter)

• history: history of one result (requires projectKey + testRunKey + resultKey)

• case: runs & results mapped to a test case (requires caseID)

Get the available test run statuses (names, plus the numeric status IDs used by bulk update endpoints). Pass projectKey to also list the users assignable to test runs.

Create a test run in a project. scope selects which test cases are included:

• all: every test case in the project

• cases: specific test cases (caseIds required)

• modules: cases from specific modules (moduleKeys required; optional mode filter)

Clone an existing test run for re-testing. All cases in the new run start as Untested.

Update the status of a single test run result, with an optional comment.

Update the status of one or more steps of a test run case. Step result keys come from get_test_case_steps.

Set one status (and optionally assignee/comment) across many results of a test run. by selects the target:

• run: every case in the run (status only)

• modules: all cases in the given modules (moduleKeys required)

• cases: the given case codes, e.g. TR001 (caseCodes required) For per-case different statuses use update_test_results_multi instead.

Update several test run results in one call, each with its own status (numeric ID: 1=Passed 2=Untested 3=Blocked 4=Retest 5=Failed 6=Not Applicable 7=In Progress 8=Hold). caseFormat says how case values identify cases:

• caseKey: the case key (e.g. MNe7x)

• code: the numeric part of the case code (TR0029 → "29"); supports per-item comments and timeSpent

• codeTR: the full case code (e.g. TR0028) Keep batches small (~20) to avoid the API's URL length limit.

Add a result to one or more test run results with a status, optional comment, time spent and file attachments (png, pdf, jpg, jpeg, gif, xls, xlsx, doc, docx, csv, log, zip, txt; max 2 MB each). Result keys come from list_test_run_results; a case key with prefix CASE (e.g. CASEaSaD) is also accepted.

List the defects of a project.

Create a new defect in a project. Use get_defect_metadata to see valid priority values. Optionally attach local files (png, pdf, jpg, jpeg, gif, xls, xlsx, doc, docx, csv, log, zip, txt; max 2 MB each).

Get the available defect statuses, severities, priorities, issue types and environments. Pass kind for a single list, or omit it for all five.

List the requirements of a project. Set includeDocuments to also return the requirement documents they are organized under.

Create a new requirement document in a project under a release.

Create a new requirement under a requirement document.