<?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 Get Track API Revision Request in Spotify for Developers</title>
    <link>https://community.spotify.com/t5/Spotify-for-Developers/Get-Track-API-Revision-Request/m-p/6571538#M16152</link>
    <description>&lt;P&gt;&lt;STRONG&gt;My Question or Issue&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;Since the major Web API update, basic track metadata such as BPM/Tempo, Key, and Scale remains inaccessible. While I understand the importance of prioritizing security and data control, these particular attributes seem fundamental and non-sensitive. The popularity metadata is already included, so extending access to these basic musical properties would align with user needs without compromising security.&lt;/P&gt;&lt;P&gt;Such metadata is essential for developers and creators who work with Spotify's ecosystem. I’m not requesting access to advanced audio features API data but rather the inclusion of these basic attributes in the Web API. Could the Spotify team consider providing these features or at least address the rationale behind their exclusion in a blog update? It’s worth noting that this data isn’t confidential; building an API wrapper to include it would be feasible but unnecessary if Spotify included it officially.&lt;/P&gt;&lt;P&gt;Thank you for considering this suggestion!&lt;/P&gt;</description>
    <pubDate>Sun, 08 Dec 2024 22:32:38 GMT</pubDate>
    <dc:creator>BringBackTheDataAPI</dc:creator>
    <dc:date>2024-12-08T22:32:38Z</dc:date>
    <item>
      <title>Get Track API Revision Request</title>
      <link>https://community.spotify.com/t5/Spotify-for-Developers/Get-Track-API-Revision-Request/m-p/6571538#M16152</link>
      <description>&lt;P&gt;&lt;STRONG&gt;My Question or Issue&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;Since the major Web API update, basic track metadata such as BPM/Tempo, Key, and Scale remains inaccessible. While I understand the importance of prioritizing security and data control, these particular attributes seem fundamental and non-sensitive. The popularity metadata is already included, so extending access to these basic musical properties would align with user needs without compromising security.&lt;/P&gt;&lt;P&gt;Such metadata is essential for developers and creators who work with Spotify's ecosystem. I’m not requesting access to advanced audio features API data but rather the inclusion of these basic attributes in the Web API. Could the Spotify team consider providing these features or at least address the rationale behind their exclusion in a blog update? It’s worth noting that this data isn’t confidential; building an API wrapper to include it would be feasible but unnecessary if Spotify included it officially.&lt;/P&gt;&lt;P&gt;Thank you for considering this suggestion!&lt;/P&gt;</description>
      <pubDate>Sun, 08 Dec 2024 22:32:38 GMT</pubDate>
      <guid>https://community.spotify.com/t5/Spotify-for-Developers/Get-Track-API-Revision-Request/m-p/6571538#M16152</guid>
      <dc:creator>BringBackTheDataAPI</dc:creator>
      <dc:date>2024-12-08T22:32:38Z</dc:date>
    </item>
  </channel>
</rss>

