<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Technical Debt on API Coding</title>
    <link>https://apicoding.com/tags/technical-debt/</link>
    <description>Recent content in Technical Debt on API Coding</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Mon, 05 Oct 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://apicoding.com/tags/technical-debt/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Finding API Endpoints, Tables and Flags Nobody Uses Takes Code and Traffic Together</title>
      <link>https://apicoding.com/finding-api-endpoints-tables-and-flags-nobody-uses-takes-code-and-traffic-together/</link>
      <pubDate>Mon, 05 Oct 2026 00:00:00 +0000</pubDate>
      <guid>https://apicoding.com/finding-api-endpoints-tables-and-flags-nobody-uses-takes-code-and-traffic-together/</guid>
      <description>&lt;p&gt;A team wants to delete &lt;code&gt;GET /v1/invoices/{id}/legacy-pdf&lt;/code&gt;. A search across the main repo finds no caller, and the gateway logs show zero hits in the last 30 days. The route goes out in a cleanup PR. On the first business day of the next quarter, a partner&amp;rsquo;s reconciliation job starts failing: it calls that endpoint four times a year, and nobody on the team knew the partner was still there.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
