<?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 Standardize 'market' parameter across Web API endpoints in Spotify for Developers</title>
    <link>https://community.spotify.com/t5/Spotify-for-Developers/Standardize-market-parameter-across-Web-API-endpoints/m-p/5186690#M2371</link>
    <description>&lt;P&gt;Many endpoints of the Spotify Web API do allow to specify a 'market' query parameter. But the usage of this parameter is not equal across all endpoints, as some endpoints explicitly require the 'market' parameter and others do not. For example, the&amp;nbsp;&lt;A href="https://developer.spotify.com/documentation/web-api/reference/#endpoint-get-playlists-tracks" target="_self"&gt;Get a Playlist's Items&lt;/A&gt;&amp;nbsp;endpoint does require the 'market' parameter, but for the&amp;nbsp;&lt;A href="https://developer.spotify.com/documentation/web-api/reference/#endpoint-get-an-albums-tracks" target="_self"&gt;Get an Album's Tracks&lt;/A&gt;&amp;nbsp;endpoint the parameter is optional.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;To simplify the Web Api I would propose to standardize the usage of the 'market' parameter across all endpoints by making the 'market' parameter optional everywhere. The endpoints that currently require, that the 'market' parameter is set, should then assume the magic value 'from_token' if the parameter is not specified. This should match the behaviour of the endpoints that currently do not require the 'market' parameter, according to my experience with the Spotify Web API.&lt;/P&gt;</description>
    <pubDate>Mon, 12 Apr 2021 13:17:26 GMT</pubDate>
    <dc:creator>sonallux</dc:creator>
    <dc:date>2021-04-12T13:17:26Z</dc:date>
    <item>
      <title>Standardize 'market' parameter across Web API endpoints</title>
      <link>https://community.spotify.com/t5/Spotify-for-Developers/Standardize-market-parameter-across-Web-API-endpoints/m-p/5186690#M2371</link>
      <description>&lt;P&gt;Many endpoints of the Spotify Web API do allow to specify a 'market' query parameter. But the usage of this parameter is not equal across all endpoints, as some endpoints explicitly require the 'market' parameter and others do not. For example, the&amp;nbsp;&lt;A href="https://developer.spotify.com/documentation/web-api/reference/#endpoint-get-playlists-tracks" target="_self"&gt;Get a Playlist's Items&lt;/A&gt;&amp;nbsp;endpoint does require the 'market' parameter, but for the&amp;nbsp;&lt;A href="https://developer.spotify.com/documentation/web-api/reference/#endpoint-get-an-albums-tracks" target="_self"&gt;Get an Album's Tracks&lt;/A&gt;&amp;nbsp;endpoint the parameter is optional.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;To simplify the Web Api I would propose to standardize the usage of the 'market' parameter across all endpoints by making the 'market' parameter optional everywhere. The endpoints that currently require, that the 'market' parameter is set, should then assume the magic value 'from_token' if the parameter is not specified. This should match the behaviour of the endpoints that currently do not require the 'market' parameter, according to my experience with the Spotify Web API.&lt;/P&gt;</description>
      <pubDate>Mon, 12 Apr 2021 13:17:26 GMT</pubDate>
      <guid>https://community.spotify.com/t5/Spotify-for-Developers/Standardize-market-parameter-across-Web-API-endpoints/m-p/5186690#M2371</guid>
      <dc:creator>sonallux</dc:creator>
      <dc:date>2021-04-12T13:17:26Z</dc:date>
    </item>
  </channel>
</rss>

