Song Requests

The redirect URI saved in your Spotify app doesn't match http://127.0.0.1:48123/callback exactly. Open your app on the Spotify dashboard → Settings → Edit, paste the address, click Add so it appears as its own line, then scroll down and click Save. Watch for a trailing slash, https, localhost or a different port. Changes can take a minute or two to apply.

The word localhost is blocked, but loopback IP addresses are allowed over plain http. That's why it uses 127.0.0.1.

Yes. Spotify only lets Premium accounts be controlled through its API. Your viewers don't need anything.

Yes, and you should: Spotify allows one development app per account. Add the redirect URI to it and use its Client ID. Its 5-user limit doesn't matter, because you are the only user.

Spotify isn't connected. Type !srsettings in your chat, open Setup and press Connect Spotify.

Requests go to Spotify about 30 seconds before the current song ends, and only while Spotify is playing. If Spotify is paused or has nothing loaded, the queue waits. Start any song and the requests follow it.

Update to 1.6.2 or newer. The usual cause: a song asked for by name or YouTube link matched a version that can’t play in your country. Spotify then skipped it without a word, or played your country’s version under a different ID, and older versions kept waiting for it for up to 20 minutes while Spotify carried on with its own music. Now the bot picks a version that plays where you are, recognises your country’s version when Spotify swaps it in, and if Spotify still drops a request, it refunds the viewer, says so in chat and moves on to the next request straight away. Requests also go to Spotify about 30 seconds before the song ends (it used to be 12), and if one still misses its turn, the bot skips Spotify’s song within its first few seconds. Songs you queued in Spotify yourself are never skipped.

Update to 1.6.4 or newer. Older versions only skipped, so Spotify played whatever it had lined up next. Now Skip (the button or !skip) first hands the next request to Spotify, waits until Spotify lists it, and then skips, so the request plays straight away. A song you queued in Spotify yourself still plays first. Skipping inside the Spotify app works a little differently: the bot can't see the button, only that the song changed early, so from 1.6.5 it hands the next request over right then and it plays after the song Spotify started. Skip once more and you're on it.

The Chat section of the window lists everything it says in chat. Reword any line (the words in {braces} are filled in for you), switch one off, or press Reset for the original. You can also have it reply under the viewer’s message instead of starting with @their name. Needs 1.8 or newer.

Connections made before 1.8 weren’t allowed to change playlists. Open Setup → Spotify connection, press Reconnect and approve it once; from then on every Spotify request that plays is added (YouTube videos aren’t on Spotify, so they’re not).

Yes, when you or a mod skip it before it played half of itself (change the share, or switch it off with 0, under Moderation → Refund early skips). That counts !skip, the Skip button, skipping or picking another song in Spotify itself, and pressing play in Spotify during a YouTube request. !voteskip and !srban don’t refund. Channel point redemptions are completed once the song has played, so they can still be refunded until then. Needs 1.9 or newer.

Moderation → No repeats for: a request that played can’t be asked for again for that many minutes. Mods can also ban it for good with !srban while it plays, or with the ban button on a request.

YouTube wouldn’t play that video in the player: either its owner blocks playing it on other sites, or YouTube wants a signed-in player (“confirm you’re not a bot”). The viewer is refunded either way. If it happens to most videos, open the YouTube player link in your normal browser where you’re signed in to YouTube instead of OBS: click Allow sound once and keep that tab open.

The YouTube player isn’t open, or Spotify is paused. The window and dock show a red bar when the player is missing: add it in OBS from Setup → YouTube. A paused Spotify holds every request, YouTube ones too; press play in Spotify or Skip.

Setup → YouTube → YouTube links → Only if the song is on Spotify. A YouTube link then only plays when that exact song (same title and artist) is on Spotify. Anything else is refused and refunded, never swapped for some other song.

Update to 1.6.7. Spotify caps how many calls a developer app may make, and every app on your Spotify developer account shares that cap. Older versions asked Spotify what's playing every 5 seconds around the clock, plus every 3 seconds while the window was open, and kept asking after Spotify said stop, so the cap ran out and Spotify blocked the app for hours. 1.6.7 asks half as often while music plays and far less when nothing does, waits as long as Spotify says, and the window and OBS dock show until when.

Update to 1.6.7. Spotify only reports a podcast episode when asked for one; 1.6.7 asks, so !song, the window and the now-playing overlay show the episode and its show.

Update to 1.6.6 or newer. Streamer.bot switches timers off when you import, and the Spotify SR Tick timer is what hands each request to Spotify near the end of a song and notices when it starts. Without it, requests only moved on a skip and stayed in Up next after they played. 1.6.6 switches the timer back on by itself, and the window and OBS dock show a red bar if it still isn't running. On an older version, open Streamer.bot → Settings → Timed Actions and tick Spotify SR Tick.

Update to 1.6.5 or newer, and check the timer above. Older versions could keep waiting for a request that had already played when Spotify was playing a long playlist, even after a restart, and the next requests waited with it. Now the bot notices within a song. If anything ever looks stuck, press Stuck? next to the song in the window or the OBS dock, or type !srreset in chat. It stops waiting for that song and keeps the rest of the queue.

No version of that song can play in your Spotify account’s country, so the bot didn’t take it (and didn’t charge for it). Ask for another version, or send a Spotify link to one that plays for you.

Open the Spotify app and press play once so it becomes the active device. In Setup → Playback device, press Refresh and pick your PC.

YouTube links are matched by the video title on Spotify, which works for official videos but can miss covers, remixes and live versions. A Spotify link or the song name with the artist is more exact.

Yes. Create the reward in Streamer.bot under Platforms → Twitch → Channel Point Rewards (so Streamer.bot can refund it), tick user input, and add a Reward Redemption trigger for it to the Spotify SR - Commands action.

Start Streamer.bot's WebSocket server under Servers/Clients → WebSocket Server and tick Auto Start. If you changed its port or set a password, build a new link with them here. Use Check my setup on the streaming PC to see which step fails.

That's OBS's browser engine failing to start, usually because a second copy of OBS is still running in the background. Close every OBS window (check the tray too), wait a few seconds, and open OBS once.

Import the new string the same way. It replaces the existing Song Requests actions and keeps your Spotify connection, settings and queue. The dock and overlay update by themselves.