Filtering endpoints

• Glob syntax
• --exclude-patterns
• --include-patterns
• Combining filters
• Examples
  • API-only spec
  • Strip static assets
  • Multiple API versions
• Pattern tips

The discover command supports glob-based filters to automate endpoint curation. This is useful for CI pipelines or large captures where manual editing is impractical.

Glob syntax

Filters use git-style glob patterns (powered by the globset crate):

--exclude-patterns

Paths matching any exclude glob are dropped entirely — they do not appear in the templates file at all.

mitm2openapi discover \
  -i capture.flow \
  -o templates.yaml \
  -p "https://api.example.com" \
  --exclude-patterns '/static/**,/images/**,*.css,*.js,*.svg,*.png'

Multiple patterns are comma-separated. A path is excluded if it matches any pattern.

--include-patterns

Paths matching any include glob are emitted without the ignore: prefix — they are auto-activated for the generate step.

mitm2openapi discover \
  -i capture.flow \
  -o templates.yaml \
  -p "https://api.example.com" \
  --include-patterns '/api/**,/v2/**'

Combining filters

When both are specified:

1. Exclude runs first — matching paths are dropped entirely
2. Include runs second — matching paths among the survivors are auto-activated
3. Everything else gets the ignore: prefix for manual review

mitm2openapi discover \
  -i capture.flow \
  -o templates.yaml \
  -p "https://api.example.com" \
  --exclude-patterns '/static/**,*.css,*.js' \
  --include-patterns '/api/**'

Result:

• /static/bundle.js — excluded (dropped)
• /api/users — included (auto-activated)
• /dashboard — neither matched (gets ignore: prefix)

Examples

API-only spec

--include-patterns '/api/**' \
--exclude-patterns '/api/internal/**,/api/debug/**'

Strip static assets

--exclude-patterns '/static/**,/assets/**,*.css,*.js,*.svg,*.png,*.jpg,*.gif,*.ico,*.woff,*.woff2'

Multiple API versions

--include-patterns '/v1/**,/v2/**,/v3/**'

Pattern tips

• Patterns match against the URL path only (after the prefix is stripped), not the full URL
• Leading / is recommended for clarity but not required
• Patterns are case-sensitive
• Use ** sparingly — it matches everything, including deeply nested paths