[Web API] Add WebSockets to the Web API for sending real-time events

[iShibi]

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.

[FAME_O]

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.

[iShibi]

People have been asking for this from Spotify for years but they aren't responding. Someone had also posted it in the ideas page but it didn't get required votes, so they closed it. I really want Spotify to be friendly with their users but it seems Spotify doesn't like open-source that much. Their API docs have a lot of mistakes which could have been fixed if they had open-sourced it on GitHub. They should learn from Discord, I like Spotify but they are really binding hands of devs like me by not listening to the requests we are making.

Spotify just release the WebSockets for everyone 🙏

[PackElend]

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 

1. https://github.com/lrholmes/spotify-connect-ws (unlikely)
2. https://github.com/TooTallNate/node-spotify-web/ --> Web Player?

[Peter_Schorn]

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.