<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Understanding PKCE Flow and Rate Limiting in Spotify for Developers</title>
    <link>https://community.spotify.com/t5/Spotify-for-Developers/Understanding-PKCE-Flow-and-Rate-Limiting/m-p/6687629#M16820</link>
    <description>&lt;P&gt;&lt;STRONG&gt;Hi, I'm integrating Spotify into my web application and have some questions about the PKCE flow. Specifically, I'm wondering about its security and purpose.&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;With PKCE, the browser receives both the access and refresh tokens. However, Spotify enforces rate limits at the application level. This raises a concern: What prevents a user from obtaining their own access and refresh tokens and using them to spam requests to Spotify? This could quickly exhaust the app-wide rate limit, affecting all users.&lt;/P&gt;&lt;P&gt;Does Spotify have a mechanism to rate-limit individual users to prevent this kind of abuse? And if not, do I need to handle per-user rate limiting on my own? If I still need to manage rate limiting server-side, what’s the purpose of using PKCE at all, if I ultimately need to proxy requests through my backend?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Plan&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;Premium&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Operating System&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;Windows 10&lt;/P&gt;</description>
    <pubDate>Sat, 01 Feb 2025 20:27:55 GMT</pubDate>
    <dc:creator>jmbogs</dc:creator>
    <dc:date>2025-02-01T20:27:55Z</dc:date>
    <item>
      <title>Understanding PKCE Flow and Rate Limiting</title>
      <link>https://community.spotify.com/t5/Spotify-for-Developers/Understanding-PKCE-Flow-and-Rate-Limiting/m-p/6687629#M16820</link>
      <description>&lt;P&gt;&lt;STRONG&gt;Hi, I'm integrating Spotify into my web application and have some questions about the PKCE flow. Specifically, I'm wondering about its security and purpose.&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;With PKCE, the browser receives both the access and refresh tokens. However, Spotify enforces rate limits at the application level. This raises a concern: What prevents a user from obtaining their own access and refresh tokens and using them to spam requests to Spotify? This could quickly exhaust the app-wide rate limit, affecting all users.&lt;/P&gt;&lt;P&gt;Does Spotify have a mechanism to rate-limit individual users to prevent this kind of abuse? And if not, do I need to handle per-user rate limiting on my own? If I still need to manage rate limiting server-side, what’s the purpose of using PKCE at all, if I ultimately need to proxy requests through my backend?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Plan&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;Premium&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Operating System&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;Windows 10&lt;/P&gt;</description>
      <pubDate>Sat, 01 Feb 2025 20:27:55 GMT</pubDate>
      <guid>https://community.spotify.com/t5/Spotify-for-Developers/Understanding-PKCE-Flow-and-Rate-Limiting/m-p/6687629#M16820</guid>
      <dc:creator>jmbogs</dc:creator>
      <dc:date>2025-02-01T20:27:55Z</dc:date>
    </item>
  </channel>
</rss>

