<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>OAuth on API Course</title>
    <link>https://apicourse.com/tags/oauth/</link>
    <description>Recent content in OAuth 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/oauth/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>API Authentication: API Keys, OAuth 2.0, and JWT Explained</title>
      <link>https://apicourse.com/api-authentication-api-keys-oauth-2.0-and-jwt-explained/</link>
      <pubDate>Sat, 02 May 2026 00:00:00 +0000</pubDate>
      <guid>https://apicourse.com/api-authentication-api-keys-oauth-2.0-and-jwt-explained/</guid>
      <description>&lt;p&gt;Authentication is where most API integrations go wrong the first time. Not because the concepts are complicated, but because there are several distinct mechanisms in common use, they solve different problems, and developers often reach for the one they recognize rather than the one that fits. Understanding what each mechanism actually does — and what it does not do — is the difference between an integration that works and one that works until it doesn&amp;rsquo;t.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
