Web API `Search` Endpoint Misinterprets `q` Parameters For `track`, `album` And `artist`
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Here's an interesting possible bug and sorry if I didn't find where it was already reported. It makes the Web API search endpoint unusable except with some "magic" accounts that receive the expected behavior, which had been present for almost two years at least.
🐞 The Web API's `Search` endpoint is behaving differently for some of my user accounts, of which I have a few from over the years. I use the `q` parameter with the embedded `track`, `album` and `artist` values to search for tracks.
URL Example: https://api.spotify.com/v1/search?q=track%3AUprising%20album%3AThe%20Resistance%20artist%3AMuse%20&t...
Expected Result:
- Results should not be returned if the keywords for track, album and artist are not present in the applicable fields of the result track
- Results should be consistent across user accounts, regardless of plan status
Actual Result:
- Many more results are returned which do not match the track, album and artist. For instance, the track named "Hysteria" from album "Absolution" by artist "Muse" is included where the `q` parameter specified "Uprising" for `name` and "The Resistance" for `album`
- Some user accounts receive the expected result while others receive this actual result
This has been happening consistently for affected accounts since about 2022-May-13. I'd be happy to provide more detail. Also, could something about the URL encoding have changed? I've been using this URL encoding scheme since November-2020 if that helps.
Country: USA
Plan: Premium Or Free Plan
Oauth Flow: Authorization Code Flow
HTTP Status: HTTP 200
Device: Google Pixel 6 Pro, Android 12
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page