List all environments (DEV, TEST, PROD, etc.) with their base URLs

List API endpoints tree with IDs, names, and folder structure. Use this to find apiDetailId values needed for creating test cases. Pass moduleId to filter by a specific service module (reduces response size significantly). Pass search to filter by endpoint name.

List test case categories (e.g. Positive, Negative, Edge Case)

List available test case tags for categorizing test cases

List available test runners (self-hosted agents for running tests)

Get endpoint test coverage statistics

List test cases (id, name, type, apiDetailId, categoryId, tagIds). Supports filtering by endpoint and pagination. Use get_test_case for full details of a single case.

Get full details of a single test case by its ID, including parameters, request body, and assertions

Create a test case for an API endpoint. Requires apiDetailId (from list_api_endpoints) and responseId. Use list_test_case_categories and list_test_case_tags first to get valid categoryId and tagIds.

Create multiple test cases at once. Each item follows the same schema as create_test_case.

Update an existing test case. Pass only the fields you want to change. The tool fetches the current state first and merges your changes, so unspecified fields are preserved.

Delete a test case by ID. This cannot be undone.

List all test scenarios (compact summary: id, name, folderId, priority, tags, description, ordering, status). Use get_test_scenario_steps for full details.

Get the steps (API calls) for a test scenario. Each step contains the full httpApiCase with parameters, auth, and request details.

Create a new test scenario (multi-step test flow). Use list_test_scenarios first to find valid folderIds and determine ordering.

Set or update the steps in a test scenario. Each step references an API endpoint via bindId (apiDetailId). Steps are fully replaced — pass the complete steps array. Supports 'http' steps (regular API calls) and 'if' conditional blocks (which have children instead of httpApiCase).

Delete a test scenario by ID. This cannot be undone.

List all test suites (compact summary: id, name, folderId, priority, tags, description, ordering, status). Use get_test_suite for full details.

Get full details of a test suite, including its items (test cases and scenarios).

Create a new test suite for CI grouping. Suites can contain test cases and test scenarios.

Replace items in a test suite. Each item is a group with a UUID, a type, and a nested array of references. For STATIC_TEST_CASE: provide testCaseIds (array of test case IDs). For STATIC_TEST_SCENARIO: provide testScenarioIds (array of scenario IDs). For DYNAMIC_TEST_CASE / DYNAMIC_TEST_SCENARIO: provide folderId to dynamically include all from that folder. This does a GET-then-merge so existing suite fields are preserved.

Delete a test suite by ID. This cannot be undone.

Create a folder for organizing test scenarios. Folders can be nested via parentId.

Delete a test scenario folder by ID. The folder must be empty. This cannot be undone.

Create a folder for organizing test suites. Folders can be nested via parentId.

List test data records for a test case. Returns metadata (id, environmentId, relatedId) but not the actual data rows — use get_test_data for that.

Get a specific test data record including the CSV data rows and column definitions.

Create a test data record for a test case. The data field is CSV-formatted: first line is the column header, subsequent lines are values. Each column needs a matching entry in the columns object. Variables are accessible in test cases as {{columnName}} or via pm.iterationData.get('columnName') in scripts.

Update an existing test data record. Fetches current state first and merges changes.

Delete a test data record by ID.