Discover · spotify.com

No picture published by spotify.com

Create native mobile and desktop apps with Spotify using PKCE

beta.developer.spotify.com spotify.com

This is what was read here when it was published. Josh Brown no longer carries it in what it publishes now.

Apps that make requests to the [Spotify Web API](/documentation/web-api/) rely on OAuth 2.0: a system that helps users authorize third-apps to access Spotify data. Since 2014, Spotify has supported three OAuth flows: the implicit grant flow, the authorization code flow, and the client credentials flow. Today, we are excited to announce that Spotify is offering support for the Proof Key for Code Exchange (PKCE) extension to the OAuth 2.0 authorization code flow. PKCE makes it easier for developers to build mobile and desktop apps that require permission from Spotify users.

More ways to use this
Open on another device
Scan this QR code to open the same public page

Scan to open this page. Your saved notes and account access are not included.

Download QR code

Open the page link

Names and references

  1. Mobile — placeQ7987530.72767,-88.05267wikidata via qlever

Keep going

Each of these is read from what this estate already kept: the feed a piece came through, the publisher behind it, the credits and topics the publisher printed. None of it is a recommendation, an identity or a record kept anywhere else.

Also from beta.developer.spotify.com

  1. Introducing Spotify SoloistSpotify spotify.com
  2. Web API quota updates for Development ModeSpotify spotify.com
  3. Introducing refresh token expirationSpotify spotify.com
  4. Update on Developer Access and Platform SecuritySpotify spotify.com
  5. Reminder: OAuth Migration - 27 November 2025Spotify spotify.com
  6. Updating the Criteria for Web API Extended AccessSpotify spotify.com