One post tagged with "api-docs"

The API spec always ends up in Confluence eventually — the review page, the integration guide, the "what does this endpoint return" discussion. And Confluence does nothing with it: paste an OpenAPI YAML into a code block and you get monospaced text that scrolls for forty screens. No endpoint tree, no expandable examples, no way to see what a 200 response looks like without reading the schema by eye. Here are the three realistic ways to get a spec onto a Confluence page, ending with the one that renders it as actual API documentation.