List all Testmo projects (id, name, run/milestone counts).

List manual test runs for a project. Supports optional name filter, open/closed filter, milestone filter and pagination.

Get a single run's summary (name, status counts, totals, milestone).

List recorded test results for a run. Note: this returns tests that have a recorded result, not necessarily every case in the run. The per-result test_id is the run_test_id needed to record a new result.

List the result statuses for a project (id → name, e.g. Passed/Failed/Blocked). Needed to know which status_id to use when recording a result.

Record a result for one test in a run. run_test_id is the test's per-run id (shown as test_id in testmo_list_results). Get valid status IDs from testmo_list_statuses.

Escape hatch: perform a raw GET against any Testmo API path (everything after /api/v1). Use for endpoints not covered by the other tools.

List workflow states for a project (run, repository_case, session). Needed for state_id when creating a run or a case.

List case templates for a project. Needed for template_id when creating cases (and to know which custom_* fields a template accepts).

List test cases in a project's repository. Supports folder/name/template filters and pagination.

Create a new manual test run in a project. Requires name, state_id (from testmo_list_states, entity 'run') and include_all. When include_all is false you must pass cases (array of case IDs).

Update a run (PATCH). Only provided fields change. Set is_closed=true to close a run (runs cannot be re-opened via the API; false is rejected).

Record results for multiple tests in a run in one request (1-100). Each item needs test_id (the per-run test id from testmo_list_results) and status_id. All items are validated before any are written — an invalid item rejects the whole batch.

Create one or more test cases (1-100) in a project's repository. Each case needs a name; folder_id/template_id/state_id are optional (defaults used). Steps and other template-specific fields go in custom with keys like custom_steps, custom_priority (must match the template or you get a 422).

Update 1-100 repository cases (PATCH). Pass ids (the cases to change) plus the fields to apply to ALL of them — the same values are written to every listed case (so name is normally used with a single id). Template custom fields go in custom (e.g. custom_steps, custom_priority) and must exist in every targeted case's template.