Strange result coming from the search end point

[Tentamens]

I originally started with the search and point and it was working just win, but then I transitioned into making the front-end ext., and when I came back to try to use the end point it was giving very strange results for instance. this is the call:

f'https://api.spotify.com/v1/search?q={"Post malone"}&type=artist"
and the first result is:
'The Post Malone Piano Cover Band'
and it even seems to be changing because before it was Postman pat

[alux]

I'm getting this issue too - like I'll search Kendrick Lamar, and the first results will be some random artists with 0 listeners. Kendrick is the 20th+ results in the response. This is also using the v1 search call.

[obiraaij]

Exact same problem. It worked fine until yesterday I think.

[Tentamens]

after looking into it further it would appear that the ordering that spotify gives randomly doesn't work.
after talking to a friend who also works with the spotify API said that it never orders to begin with so seems like there's some bug or they never wanted it to be orders in the first place
(for anyone checking this thread having the same issue you can just use something like Levenshtein if on python and just search through the artists names and get the "closest" to the input field that works pretty well for me)

[cmijack]

Having the same issue - first noticed yesterday but used the search endpoint for finding artists for well over a year prior to this and the ordering was logical and worked well.

Sorting on the front-end isn't ideal as in some cases we need to search for smaller artists and will need to take advantage of pagination - to properly sort this way on the front-end we would need to first page all results which is wildly impractical.

Can only assume that a bug has been introduced during a recent change. Really could do with this fixing as soon as possible.