<?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 WebAPI and the SimplifiedAlbumObject in Spotify for Developers</title>
    <link>https://community.spotify.com/t5/Spotify-for-Developers/WebAPI-and-the-SimplifiedAlbumObject/m-p/7063015#M18492</link>
    <description>&lt;P&gt;I'm seeing a few inconsistencies that I was hoping SPOTIFY could help with:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;#1 - Up until yesterday, when retrieving albums via the /artists/{id}/albums request, the albums being returned included external_ids, copyrights, [record] label, and popularity. &amp;nbsp;As of today, that seems to have changed, and now I'm seeing album objects that are missing those fields. &amp;nbsp;What changed? &amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;#2 - When attempting to retrieve an artist id and their corresponding albums, I would typically do a /search with parameter type = artist, get a series of artist_ids, and then for each, issue the /artists/{id}/albums request. &amp;nbsp;However, I am now encountering 429 errors on the albums request with this approach. &amp;nbsp;As an alternative, I've opted to expand the /search request and change the 'type' parameter to 'artist,album' which returns a payload of both artists AND albums. &amp;nbsp;This seems to work without causing a 429 -- why? &amp;nbsp; My only issue with this path is that the album objects fail to include the aforementioned fields -- copyrights, external_ids, label, and popularity.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;#3 - The /artists/{id}/albums request allows me to limit the returning payload with the 'include_groups' parameter, thereby enabling me to ignore singles or compilations (for example). &amp;nbsp;Is there a way to extend this server-side filtering to the basic /search query? &amp;nbsp;It would go a long way toward minimizing the size of returning payloads.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Wed, 23 Jul 2025 18:39:04 GMT</pubDate>
    <dc:creator>slieb17</dc:creator>
    <dc:date>2025-07-23T18:39:04Z</dc:date>
    <item>
      <title>WebAPI and the SimplifiedAlbumObject</title>
      <link>https://community.spotify.com/t5/Spotify-for-Developers/WebAPI-and-the-SimplifiedAlbumObject/m-p/7063015#M18492</link>
      <description>&lt;P&gt;I'm seeing a few inconsistencies that I was hoping SPOTIFY could help with:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;#1 - Up until yesterday, when retrieving albums via the /artists/{id}/albums request, the albums being returned included external_ids, copyrights, [record] label, and popularity. &amp;nbsp;As of today, that seems to have changed, and now I'm seeing album objects that are missing those fields. &amp;nbsp;What changed? &amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;#2 - When attempting to retrieve an artist id and their corresponding albums, I would typically do a /search with parameter type = artist, get a series of artist_ids, and then for each, issue the /artists/{id}/albums request. &amp;nbsp;However, I am now encountering 429 errors on the albums request with this approach. &amp;nbsp;As an alternative, I've opted to expand the /search request and change the 'type' parameter to 'artist,album' which returns a payload of both artists AND albums. &amp;nbsp;This seems to work without causing a 429 -- why? &amp;nbsp; My only issue with this path is that the album objects fail to include the aforementioned fields -- copyrights, external_ids, label, and popularity.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;#3 - The /artists/{id}/albums request allows me to limit the returning payload with the 'include_groups' parameter, thereby enabling me to ignore singles or compilations (for example). &amp;nbsp;Is there a way to extend this server-side filtering to the basic /search query? &amp;nbsp;It would go a long way toward minimizing the size of returning payloads.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 23 Jul 2025 18:39:04 GMT</pubDate>
      <guid>https://community.spotify.com/t5/Spotify-for-Developers/WebAPI-and-the-SimplifiedAlbumObject/m-p/7063015#M18492</guid>
      <dc:creator>slieb17</dc:creator>
      <dc:date>2025-07-23T18:39:04Z</dc:date>
    </item>
  </channel>
</rss>

