<?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 Do I need to make a developer account for this? in Spotify for Developers</title>
    <link>https://community.spotify.com/t5/Spotify-for-Developers/Do-I-need-to-make-a-developer-account-for-this/m-p/7309936#M19713</link>
    <description>&lt;P&gt;I'm trying to set up Spotify integration in Home Assistant, where I was directed here to make a Developer account, create app, and supply the Oauth details in HA.&amp;nbsp;&lt;BR /&gt;Now I consider this logic not valid, as I'm not a developer who uses Spotify API for developing 3rdparty apps. Why would I need to make a developer account for this?&lt;BR /&gt;I also saw a couple of other integration types in forum, where it does use the same logic.&lt;BR /&gt;The common understanding about this topic is that we don't need to supply uname/password for this in the integration and access can be revoked anytime in spotify settings when not needed anymore. And we cannot be logged out when oauth cred is active, like sometimes for uname/passwd solution.&lt;/P&gt;&lt;P&gt;My suggestion would be to make Oauth credential generation for the user account available inside the main Spotify website and apps. And let us who are not devs using Spotify API, but need OAuth credentials for existing integrations as users, to use this credential.&lt;BR /&gt;Would this be feasible?&lt;/P&gt;</description>
    <pubDate>Mon, 19 Jan 2026 20:03:58 GMT</pubDate>
    <dc:creator>adtewa</dc:creator>
    <dc:date>2026-01-19T20:03:58Z</dc:date>
    <item>
      <title>Do I need to make a developer account for this?</title>
      <link>https://community.spotify.com/t5/Spotify-for-Developers/Do-I-need-to-make-a-developer-account-for-this/m-p/7309936#M19713</link>
      <description>&lt;P&gt;I'm trying to set up Spotify integration in Home Assistant, where I was directed here to make a Developer account, create app, and supply the Oauth details in HA.&amp;nbsp;&lt;BR /&gt;Now I consider this logic not valid, as I'm not a developer who uses Spotify API for developing 3rdparty apps. Why would I need to make a developer account for this?&lt;BR /&gt;I also saw a couple of other integration types in forum, where it does use the same logic.&lt;BR /&gt;The common understanding about this topic is that we don't need to supply uname/password for this in the integration and access can be revoked anytime in spotify settings when not needed anymore. And we cannot be logged out when oauth cred is active, like sometimes for uname/passwd solution.&lt;/P&gt;&lt;P&gt;My suggestion would be to make Oauth credential generation for the user account available inside the main Spotify website and apps. And let us who are not devs using Spotify API, but need OAuth credentials for existing integrations as users, to use this credential.&lt;BR /&gt;Would this be feasible?&lt;/P&gt;</description>
      <pubDate>Mon, 19 Jan 2026 20:03:58 GMT</pubDate>
      <guid>https://community.spotify.com/t5/Spotify-for-Developers/Do-I-need-to-make-a-developer-account-for-this/m-p/7309936#M19713</guid>
      <dc:creator>adtewa</dc:creator>
      <dc:date>2026-01-19T20:03:58Z</dc:date>
    </item>
  </channel>
</rss>

