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...
I have noticed that the preview_url field is always null when using the Client Credentials flow and I don't see any thing in the documentation describing what flows have access to preview urls. Is this an intended feature, just not documented(maybe it is but I can't find it), or is this a bug in the API? Any other information about this would be greatly appreciated.
I still have this problem too. I used this spotify search api to get preview url of any tracks. Then today I found I preview_url of all tracks are null. I hope this is just a serios bug. I found `deprecated` in document though...
Same issue here, it seems deprecated after they removed a lot of features on 27th November 2024. https://community.spotify.com/t5/Spotify-for-Developers/Changes-to-Web-API/td-p/6540414
Same issue here, it seems like they intentionally deprecated it after they removed a lot of features on 27th November 2024. https://community.spotify.com/t5/Spotify-for-Developers/Changes-to-Web-API/td-p/6540414.
Im on Spotify support chat right now, they are going to get me in touch with the development team as we speak..
Update:
Hello there! Camsey here. Nice to meet you. I'm here to assist you with your issue today. Kindly give me a few minutes to review the details you've sent, I'd be glad to help.
Camsey at 03:41 PM, Nov 28
Hi. Yesterday you deprecated the SPotify Web API. https://developer.spotify.com/blog/2024-11-27-changes-to-the-web-api
You at 03:41 PM, Nov 28
Without any warning... now my app that uses the 30 second previews does not work anymore. Is there some replacement available
You at 03:42 PM, Nov 28
Thanks for waiting! I understand your concern. No worries, we will figure this out. Just give me a couple of minutes while I review your account.
Camsey at 03:44 PM, Nov 28
Ok
You at 03:46 PM, Nov 28
I've checked, and there's some exciting news about Web IPI! The updates are impressive, and the innovation is amazing. Stay tuned to this page for updates in the next few days!
Camsey at 03:49 PM, Nov 28
What?
You at 03:49 PM, Nov 28
You just removed functionalities, so that all type of applications do not work anymore. Do you expect replacements for this
You at 03:50 PM, Nov 28
https://community.spotify.com/t5/Spotify-for-Developers/Changes-to-Web-API/td-p/6540414
You at 03:50 PM, Nov 28
80+ people are already complaining under 24 hours
You at 03:50 PM, Nov 28
What I meant is that in the next few days, a replacement is coming, and there's an exciting innovation that customers like you will enjoy. I understand this is happening a bit early without prior updates.
Camsey at 03:52 PM, Nov 28
Ok, so the functionality will be replaced?
You at 03:53 PM, Nov 28
Ok great
You at 03:54 PM, Nov 28
That's correct! No worries about that.
Camsey at 03:54 PM, Nov 28
It is a bit strange though, that you completely deprecate the old functionality. Can't you give us access to the deprecated functionalities a bit longer, so that we have time to refactor to the new ones when they release?
You at 03:55 PM, Nov 28
Isn't that a way smoother operation?
You at 03:55 PM, Nov 28
Since the development team is handling the changes, I'll reach out to them right away to address your request immediately.
Camsey at 03:57 PM, Nov 28
Yes please
You at 03:57 PM, Nov 28
I think I speak for 100+ people
You at 03:57 PM, Nov 28
Right now, you can join the forum here: https://community.spotify.com/t5/Spotify-for-Developers/Changes-to-Web-API/td-p/6540414. This way, the development team will see that many users are affected by these changes. Since the replacement is coming soon, it makes sense to extend the functionality, don't you think?
Camsey at 04:00 PM, Nov 28
I already did
You at 04:00 PM, Nov 28
Great! Give me a minute or two to get in touch with the development team. Hang on a bit.
I was able to get around this by using my own personal access token using the OAuth flow but now it doesn’t due to the recent changes in Spotify’s API.
Thank you for reaching out to the devs. I noticed this yesterday and posted about it in a discord server and when checking your reply I saw the pinned message about it on the forum.
Hello guys, our app is currently broken due to this issue. Can you please provide us with clear instructions about how to get values for preview_url?
As of right now, there is no way to get preview URLs. However the links to previews are still active if you have any cached.
I found they said "These changes will impact ... Existing apps that are still in development mode without a pending extension request". So I expect they will allow me to access preview_url after my app will be in quota mode. What do you guys think about this?
https://developer.spotify.com/blog/2024-11-27-changes-to-the-web-api
If you already have a pending request then I think you should have access. That’s is how I’m interpreting it.
What if i have not sent a request yet...?
Hello,
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…