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.
Add WebSockets to the Web API for sending real-time events like play, pause, skip and more. This way the users of the API will not have to make frequent requests for these kinds of data and will get the data when these events happens. This will really help library devs like me and will save a lot of unnecessary requests to your servers. I'll suggest making it on the line of Discords Gateway API.
I was just thinking this. This is holding Spotify dependent innovation behind. I'm working on a embedded system and if another streaming service had to offer web sockets, I would ditch Spotify. I would also have to tell my customers that my product wont work with Spotify.
Does the Discord API provide options when you connect Spotify with Discord? (https://stackoverflow.com/questions/51528806/spotify-webhooks/51569606#comment134771655_51569606) as a workaround?
I found some old projects on GitHub but I don't think they allow to send real-time events
It should also be noted that Spotify already has private web socket APIs that it uses for its native clients. All it needs to do is open-source and document them.
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…