Import, Export, And Quality Gates

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.

Always use current CLI help for exact arguments. Before import, check file format, OpenAPI quality gates, route-skeleton risk, tag grouping, native-format module strategy, ignoreCount, and whether a clean validation project is needed. After import, agents must verify results with agentHints, list/get, and, when relevant, run/report. Do not treat an import command returning success as complete by itself.

When To Use

• Generate API specs from code, PRDs, requirement documents, test documents, or discussions and import them into Apidog.
• Import OpenAPI, Postman, HAR, Apidog native format, or other project data.
• Configure automatic import.
• Export OpenAPI, Markdown, HTML, Postman, or Apidog native format.
• Determine whether a generated spec is only a route skeleton.
• Migrate, back up, or copy Apidog projects, especially when module reuse or new module creation must be controlled.

When Not To Use

• Import or copy existing endpoints, test cases, or scenario steps into a test scenario: use apidog-test-scenario with test-scenario import-steps or test-scenario add-ref.
• Precisely maintain scenario steps, variables, assertions, or processors: use apidog-test-scenario.