Spotify Search API Issue - 404 not found

[sean91]

There currently seems to be an issue with the Search API - basic queries are suddenly and randomly returning "404 not found" errors.

Sometimes the exact same query works after a few retries.

The status page at https://status.spotify.dev does not yet reflect it.

Is this a known issue and is someone looking into it? And is anyone else experiencing the same behaviour?

I'll attach an img from the tryout section of the official docs at https://developer.spotify.com/documentation/web-api/reference/search, where the issue can be reproduced.

Thanks!

[sean91]

@Riebmann Offset works for me, if I make sure to match up the limit and the offset parameters, so there's no overlap (offset is 0 or a multiple of limit). Might be caching is set up to work this way. Anyways probably not related to this issue.

[Riebmann]

My Impl with offset worked before like a charm. I wanted to receive e.g. 30 Top-Tracks of an artist.

Top-Tracks yields max 10 tracks- so I tried to fetch another 10 with an offset of 10 - and so on.

Now I just receive 3 times the same 10 Tracks

[sean91]

@Riebmann Ah okay, you're talking about a different endpoint then. I can't see an offset parameter defined for the /top-tracks endpoint; so that functionality might also have been removed (https://developer.spotify.com/documentation/web-api/reference/get-an-artists-top-tracks). I would open a separate topic to investigate this.

(to achieve something similar, you could perhaps also use the /search endpoint, use type=track and q={artistName} with a limit at 30-50, and then order the tracks by popularity)

[aspleenic]

It seems like the offset issue is separate. I've taken the liberty of starting a new thread on this topic.

[adrianszabat]

I'm experiencing the same issue. Sometimes and randomly a simple query like get track return this error. Then I try again and everything seems to work fine.

[Ashugh]

Have Same Issue 

[Ashugh]

I have same issue