Web API `search` endpoint unexpected results.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi,
The Web API's `search` endpoint is giving unexpected results. For example, the result is empty (even after the response code 200). BUT, with the same query on documentation playground, it does return right results. Even if I copy-paste the exact query from the documentation playground (after it returns expected results) into my code, it returns empty results unlike the documentation playground or the Spotify web interface.
Then, I thought I might be doing something wrong, AND the thing was: I was using `track:` & `artist:` before the song name and artist name respectively just like shown in the documentation example. Even tried with explicitly using `track%3A` & `artist%3A`, but still got empty/null results with response code 200.
So, I removed `track:` & `artist:` from my query string. But now I am getting unexpected results again. It does not return right results. Same search query if compared with the Web interface & Documentation playground, it (the `search` endpoint) returns completely different / random results.
Again, even if copy-paste the exact same query from documentation playground (which returns expected results) into the code, the `search` endpoint returns empty/null results.
^ <Response [200]>, but "items" list is empty.
^ Same query on Documentation playground return "items".
(new here, sorry if the issue isn't clear or I repeated myself)
- Labels:
-
Possible Bug
-
Web API
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page