<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Swagger on API Course</title>
    <link>https://apicourse.com/tags/swagger/</link>
    <description>Recent content in Swagger on API Course</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Sat, 02 May 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://apicourse.com/tags/swagger/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>OpenAPI and Swagger: Documenting Your API the Right Way</title>
      <link>https://apicourse.com/openapi-and-swagger-documenting-your-api-the-right-way/</link>
      <pubDate>Sat, 02 May 2026 00:00:00 +0000</pubDate>
      <guid>https://apicourse.com/openapi-and-swagger-documenting-your-api-the-right-way/</guid>
      <description>&lt;p&gt;Documentation is the first thing a developer encounters and the last thing most teams prioritize. The result is a familiar pattern: the API is built, the launch deadline approaches, documentation gets written in a hurry by someone who did not build the API and does not fully understand it, and integrators spend the next six months filing support tickets that could have been answered by better documentation. OpenAPI exists to break that cycle by making documentation a first-class artifact of the API itself.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
