<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>URL Design on API Course</title>
    <link>https://apicourse.com/tags/url-design/</link>
    <description>Recent content in URL Design 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/url-design/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>REST Resource Modeling: How to Design URLs That Make Sense</title>
      <link>https://apicourse.com/rest-resource-modeling-how-to-design-urls-that-make-sense/</link>
      <pubDate>Sat, 02 May 2026 00:00:00 +0000</pubDate>
      <guid>https://apicourse.com/rest-resource-modeling-how-to-design-urls-that-make-sense/</guid>
      <description>&lt;p&gt;REST APIs organize their surface around resources — the nouns of your domain. How you identify, name, and structure those resources determines whether your API feels intuitive or requires constant documentation reference. Good URL design is not aesthetic preference. It is communication: URLs tell developers what the API contains, how it is organized, and how to navigate it. Done well, a developer can infer what endpoints exist from the ones they already know.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
