Type in your question below and we'll check to see what answers we can find...
Loading article...
Submitting...
If you couldn't find any answers in the previous step then we need to post your question in the community and wait for someone to respond. You'll be notified when that happens.
Simply add some detail to your question and refine the title if needed, choose the relevant category, then post.
Before we can post your question we need you to quickly make an account (or sign in if you already have one).
Don't worry - it's quick and painless! Just click below, and once you're logged in we'll bring you right back here and post your question. We'll remember what you've already typed in so you won't have to do it again.
Please see below the most popular frequently asked questions.
Loading article...
Loading faqs...
Please see below the current ongoing issues which are under investigation.
Loading issue...
Loading ongoing issues...
Hi,
I am running a Spotify service for many years but recently the "/v1/me/following" is not working correctly.
The endpoints retrieves a list of artists that the user is following with a maximum limit of 50. With a cursor id the the next 50 can be retrieved until the cursor has a null value so all data has been retreived.
When testing with my account (I follow 1619 artists) the first 50 can be retrieved but when passing the cursor id as after parameter the next list is empty.
The problem can be reproduced in the console: https://developer.spotify.com/console/get-following/
Has there been a change lately? Because I am sure this worked before.
I can confirm this problem happens to me and a few other people using my app. The first call to "v1/me/following?limit=50&type=artist" returns 50 artists correctly, but the included "next" URL returns an empty array with "next" being null, thus ending the loop early. This was working correctly for the past few years, it only started happening recently
The same thing happened to me; I was losing my mind trying to figure out what I was doing wrong. Glad to see I'm not the only one facing this issue.
The "after" parameter was supposed to be an artist's ID. But that's no longer the case. I'm getting eg.
&after=v6uTp6FjUj7+sexyt5uxYSOBOobA86/y/btNybITAWw=
But even replacing the "after" parameter with a valid ID I wouldn't get any correct result.
Seems to be working again. As of a few minutes ago both my application and the dev portal now see valid data again.
Yep, it's back, smh it really messed things up on my app.
I'm still having issues with the /v1/me/top/artists endpoint returning { href: null, followers: 0 } for followers for all time ranges and artists. I don't know if this has anything to do with this topic, but I haven't seen anyone else talk about it yet so I wanted to check if any of ya'll have encountered this issue before I start a topic about it.
Hey there you, ย Yeah, you!ย 😁 ย Welcome - we're glad you joined the Spotify Community! ย While you here, let's have a fun game and getโฆ