<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Deprecation on API Course</title>
    <link>https://apicourse.com/tags/deprecation/</link>
    <description>Recent content in Deprecation 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/deprecation/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>API Deprecation: How to Retire Endpoints Without Burning Integrators</title>
      <link>https://apicourse.com/api-deprecation-how-to-retire-endpoints-without-burning-integrators/</link>
      <pubDate>Sat, 02 May 2026 00:00:00 +0000</pubDate>
      <guid>https://apicourse.com/api-deprecation-how-to-retire-endpoints-without-burning-integrators/</guid>
      <description>&lt;p&gt;Every API feature eventually reaches the end of its useful life. The endpoint was designed before the domain was understood. The schema made assumptions that no longer hold. A better approach exists. The old version must go. How you handle that retirement determines whether your API&amp;rsquo;s integrators trust you or resent you.&lt;/p&gt;&#xA;&lt;p&gt;Deprecation done well is a communication and scheduling problem. Deprecation done poorly is a breaking change that happens without warning.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
