API Test Cases

Prerequisite: read ../apidog-cli/SKILL.md first. If the stable entry skill conflicts with this domain skill, use the current CLI help and this skill as the source of truth. For API definitions, follow current CLI help for endpoint, schema, folder, and related commands. For multi-step flows, read ../apidog-test-scenario/SKILL.md.

Always use the current CLI help for exact arguments. When creating or updating API test cases, pay special attention to categoryId display risks, the boundary between test-case and test-scenario, requestBody/processor/assertion/extractor structure, and run-time verification. Agents must validate payloads with cli-schema validate before writing, then use get to confirm the saved structure.

When To Use

• Create automated test cases under a single endpoint.
• Update test steps, assertions, variable extractors, and pre/post processors.
• List test cases under an endpoint.
• Run API test cases by caseId, endpointId, or categoryId.
• Create or maintain test datasets.
• Diagnose issues such as missing test steps in the client, ineffective assertions, or empty extracted variables.

When Not To Use