Announcements

Help Wizard

Step 1

NEXT STEP

FAQs

Please see below the most popular frequently asked questions.

Loading article...

Loading faqs...

VIEW ALL

Ongoing Issues

Please see below the current ongoing issues which are under investigation.

Loading issue...

Loading ongoing issues...

VIEW ALL

Not receiving results when searching by ISRC

Solved!

Not receiving results when searching by ISRC

I'm trying to search the web api for songs by ISRC but I no longer receive any results, only an empty items array. My search query looks like this: https://api.spotify.com/v1/search?query=isrc:USLZJ1613311

 

I've even tried on the spotify web console but that no longer gives me results either, just an empty items array. Just a few days ago this worked in both my app and on the web console.

 

 

Reply

Accepted Solutions
Marked as solution

Okay, we figured it out. There was an ongoing experiment within an upstream system that was causing this issue for users part of that experiment. We have stopped the experiment and I am able to verify that "artist:eminem" is returning the correct tracks as expected (and as users not part of the experiment were getting). Are you able to confirm this on your end as well?

View solution in original post

21 Replies

Hi @ndubs

 

I've just tested it, and I did get a result when specifying the required type track.

 

I hope this helps.

 

Cheers!

XimzendSpotify Star
Help others find this answer and click "Accept as Solution".
If you appreciate my answer, maybe give me a Like.
Note: I'm not a Spotify employee.

My apologies @Ximzend  I totally didn't add that in the query on my initial post. This is query including the type=track:  https://api.spotify.com/v1/search?query=isrc%3AUSLZJ1613311&type=track

 

I just tried this and I'm still not receiving any results

 

No problem.

The other thing I noticed now is that you use the word query instead of the letter q. It has to be a q.

XimzendSpotify Star
Help others find this answer and click "Accept as Solution".
If you appreciate my answer, maybe give me a Like.
Note: I'm not a Spotify employee.

What about when I plug it into the console on the docs? 

query.PNG

Thank you for the screenshot.

I have reported this bug of the console, so someone can look into it.

XimzendSpotify Star
Help others find this answer and click "Accept as Solution".
If you appreciate my answer, maybe give me a Like.
Note: I'm not a Spotify employee.

Sounds good, thank you for your help.

Both `q` and `query` should work, but you need to choose one of them, you cannot use both in the same request. I was also able to do the request mentioned in this thread and get back a matching track. Is this still an issue?

It's still not working for me. I attempted the query again both in my own app and on the console and it's giving me an empty items array as a result:

https://api.spotify.com/v1/search?query=isrc:USLZJ1613311&type=track

 

 

 

It's also not working for me.

Screenshot 2024-11-19 at 13.18.08.png

I have two spotify accounts. It's working on one, but not the other.

I just tested the same on a new account and it worked for me but not the other as well. Would love to know what's going on.

After URL encoding : into %3A I am getting a result (isrc%3AUSLZJ1613311), are you able to reproduce this as well?

 

When testing with two different accounts, are all other things identical?

it's also not working for me

When testing with the two different accounts things are identical. I went ahead a tried to use the %3A for the colon and it didn't work for me. The api returns results but the results are completely unrelated to the isrc that I'm searching for.

other filters are not working for me as well, not just isrc

tuannamnguyen_0-1732677650529.png

 

encoding works however none of the returned results are relevant to my search terms

I tried changing the query to "artist%3Aeminem" and I get a result featuring eminem. But some that are not related to eminem.. will continue to investigate..

Marked as solution

Okay, we figured it out. There was an ongoing experiment within an upstream system that was causing this issue for users part of that experiment. We have stopped the experiment and I am able to verify that "artist:eminem" is returning the correct tracks as expected (and as users not part of the experiment were getting). Are you able to confirm this on your end as well?

Just confirmed that it is working now with my original query.

Suggested posts