Search Endpoint Bug - Response Inconsistency With Bearer Tokens

[cmijack]

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 https://developer.spotify.com/documentation/web-api/reference/search - 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.

However when using a bearer token obtained using our Spotify Web App the top result is a track "Aarena (Knock2 Remix)" by ISOxo.

URL:

'https://api.spotify.com/v1/search?q=A.R.E.A.%2520track%3Aon&type=track&market=GB&limit=10&offset=0'

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.

[Ximzend]

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.