Intelliflo Public API Report & Swagger Generator

You can automate consolidated swagger generation by filtering operations using PublicApi attributes or an API Gateway whitelist, then applying OpenAPI 3.0 templating to fetch and merge v1 and v2 swagger files into a unified output.

API Gateway whitelist filtering works by extracting GitHub data to identify permitted operations, cross-referencing them against your service swagger definitions, and excluding any endpoints not explicitly authorized for portal-ready documentation.

Yes, the generation workflow outputs both markdown API reports and OpenAPI 3.0 swagger artifacts simultaneously. The markdown provides a readable inventory while the swagger files supply the structured specification for portal publication.

The best way to consolidate swagger versions is using Public Swagger v2 as the canonical template structure, which captures OAuth scopes and server metadata while tracking portal status for each operation across both versions.

Yes, GitHub data extraction is required to identify and filter PublicApi attributes across your repositories. This extraction provides the necessary repository metadata to determine which operations belong in the consolidated public API report.

You need to regenerate consolidated public API swagger files when services are updated, new endpoints receive PublicApi attributes, or API Gateway whitelist configurations change, ensuring portal documentation accurately reflects the current authorized operations.