<?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 Re: Search Endpoint Bug - Response Inconsistency With Bearer Tokens in Spotify for Developers</title>
    <link>https://community.spotify.com/t5/Spotify-for-Developers/Search-Endpoint-Bug-Response-Inconsistency-With-Bearer-Tokens/m-p/5727736#M11780</link>
    <description>&lt;P&gt;&lt;SPAN&gt;I've noticed this behavior, and I believe it's intentional rather than a bug: showing search results that are more relevant to the user who's logged in. You'll observe a similar pattern when searching for something using different accounts across the web, desktop, or mobile apps.&lt;/SPAN&gt;&lt;/P&gt;</description>
    <pubDate>Tue, 05 Dec 2023 19:06:05 GMT</pubDate>
    <dc:creator>Ximzend</dc:creator>
    <dc:date>2023-12-05T19:06:05Z</dc:date>
    <item>
      <title>Search Endpoint Bug - Response Inconsistency With Bearer Tokens</title>
      <link>https://community.spotify.com/t5/Spotify-for-Developers/Search-Endpoint-Bug-Response-Inconsistency-With-Bearer-Tokens/m-p/5727315#M11779</link>
      <description>&lt;P&gt;The search endpoint is returning different responses based on the bearer token given. When I use the bearer token generated by the web API documentation interface at&amp;nbsp;&lt;A href="https://developer.spotify.com/documentation/web-api/reference/search" target="_blank" rel="noopener"&gt;https://developer.spotify.com/documentation/web-api/reference/search&lt;/A&gt;&amp;nbsp;- I get results I expect, for example using the url below I get the the top result of a track called "On The Go" by A.R.E.A.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;However when using a bearer token obtained using our Spotify Web App the top result is a track&amp;nbsp;&lt;SPAN class=""&gt;"Aarena (Knock2 Remix)" by&amp;nbsp;&lt;/SPAN&gt;&lt;SPAN class=""&gt;ISOxo.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;URL:&lt;/P&gt;&lt;DIV&gt;&lt;DIV&gt;&lt;SPAN&gt;'https:&lt;/SPAN&gt;&lt;SPAN&gt;//api.spotify.com/v1/search?q=A.R.E.A.%2520track%3Aon&amp;amp;type=track&amp;amp;market=GB&amp;amp;limit=10&amp;amp;offset=0'&lt;BR /&gt;&lt;BR /&gt;This is rendering our search functionality useless. The results returned to our web app are far off what you would expect. I can only assume this is some kind of bug as I posted a similar bug a few months ago here that was resolved within the coming weeks. Hoping you can tend to this one quickly. Thanks.&lt;/SPAN&gt;&lt;/DIV&gt;&lt;/DIV&gt;</description>
      <pubDate>Tue, 05 Dec 2023 15:37:19 GMT</pubDate>
      <guid>https://community.spotify.com/t5/Spotify-for-Developers/Search-Endpoint-Bug-Response-Inconsistency-With-Bearer-Tokens/m-p/5727315#M11779</guid>
      <dc:creator>cmijack</dc:creator>
      <dc:date>2023-12-05T15:37:19Z</dc:date>
    </item>
    <item>
      <title>Re: Search Endpoint Bug - Response Inconsistency With Bearer Tokens</title>
      <link>https://community.spotify.com/t5/Spotify-for-Developers/Search-Endpoint-Bug-Response-Inconsistency-With-Bearer-Tokens/m-p/5727736#M11780</link>
      <description>&lt;P&gt;&lt;SPAN&gt;I've noticed this behavior, and I believe it's intentional rather than a bug: showing search results that are more relevant to the user who's logged in. You'll observe a similar pattern when searching for something using different accounts across the web, desktop, or mobile apps.&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 05 Dec 2023 19:06:05 GMT</pubDate>
      <guid>https://community.spotify.com/t5/Spotify-for-Developers/Search-Endpoint-Bug-Response-Inconsistency-With-Bearer-Tokens/m-p/5727736#M11780</guid>
      <dc:creator>Ximzend</dc:creator>
      <dc:date>2023-12-05T19:06:05Z</dc:date>
    </item>
  </channel>
</rss>

