Join GitHub today
Search endpoints return 404 Not Found if query contains the slash '/' character #187
We stumbled across an issue when using the slash
The response is a
The characters that are not valid in a search query should be documented so people are able to strip them from the query.
This used to work, so I'm not sure if it's an intentional exclusion that needs documentation or just a regression that should be fixed (and I'd argue it's the latter).
One query in particular that has worked for a while but is now broken is https://api.spotify.com/v1/search?q=De%2FVision&type=artist, which should match https://play.spotify.com/artist/1bN9idF4rgIhaaKFpwgzoQ (De/Vision). I've had to update code to replace slashes with spaces so the query is now https://api.spotify.com/v1/search?q=De+Vision&type=artist, but that's incorrect, since it would allow for "De Vision" (if they existed) to be the better match when the intent was De/Vision.