OBS Control Dock Guide - Social Stream Ninja

Quick setup

In Social Stream Ninja, open Global settings and tools → Mechanics.
Avatud OBS Control Dock and copy its link. Keep Social Stream Ninja active during the stream.
The copied link includes your session, password, and connection settings.
In OBS, open Docks → Custom Browser Docks.
Name the dock Social Stream Controls and paste the copied link. For a session without a password or server settings, the URL is:

https://socialstream.ninja/obs-control-dock.html?session=YOUR_SESSION_ID

Select Apply, close the settings window, and place the new dock where you want it in OBS.
Confirm the dock says Connected. If the URL did not include a session, enter it in the dock and select Save & connect.

Open the Control Dock

Which server settings are required?

The generated control link follows Social Stream's connection settings. Normal links use P2P. When Dock sends its commands to Extension via server is enabled, controls use that server connection.

For a manually configured API connection, add &server (või &server=wss://YOUR_SERVER) and enable remote API control of extension.

OBS's WebSocket Server Settings are unrelated and can remain off.

Using it with end-of-stream Credits

Before the stream, set Credits Trigger Mode juurde Background collection. This lets the app collect chatters, members, and donors while the Credits Browser Source is closed.
Add the generated Credits URL to the OBS ending scene using the same Session ID.
At the end of the stream, switch to the ending scene first so the Credits Browser Source is loaded and connected.
Select Start Credits in the OBS control dock.

Load before Start: background collection can work while the Credits page is closed, but Start, Preview, and Test need a connected Credits Browser Source to display anything.

Vt Credits Roll Guide for collection modes, filters, and troubleshooting missing names.

What each Credits button does

Button	Result
Start Credits	Runs the real collected list.
Preview	Runs the real list without consuming page-collected entries.
Test Credits	Displays built-in participant, member, and donor examples. It does not prove that real names were collected.
Reset Saved Credits	Clears the saved Background collection for the active Social Stream session.

Products & support links

In Social Stream, open Monetization, save and enable your products, then choose Open OBS control dock. Copy that private control URL into OBS's Custom Browser Docks. For a products-only dock, use obs-control-dock.html?session=YOUR_SESSION_ID&commerce.

Keep Social Stream on and use the generated Product Controls link. Add the separate monetization overlay URL as an OBS Browser Source for viewers. The control dock is for you; never share its session URL with viewers.

OBS product controls with a saved product selector, duration, Show, Next, Hide products, Resume schedule, and selected product state

Show: select a saved product and pin it. Next: advance from the current product.
Hide products: hide promotional cards; activity alerts continue. Resume schedule: return to your saved first-product or rotation setting.
Duration: Show, Next, and Hide return to the saved schedule after this many seconds. Use 0 to keep the override until changed.
State: refreshes every five seconds while this section is open. It reports Social Stream's selection, not whether an OBS scene is visible. Lost or unconfirmed connections disable product buttons until state is available again.

The dock, popup, Stream Deck, and Event Flow share the same controls. Edit and save the catalog in Social Stream. See Product controls for setup and automation.

Other controls and their required pages

Featured Chat: keep the normal Streaming Chat Dock and featured overlay connected on the same session.
Timer: keep the Timer page connected on the same session if it needs to display the timer.
Waitlist & Giveaway: configure the waitlist in Social Stream first; Reset clears the current entries.

The dock reconnects automatically if the API connection drops. A green Connected status only confirms the control connection; the target page still needs to be open when a command displays something.

Direct API examples

The same buttons can be scripted with HTTP GET requests:

https://io.socialstream.ninja/SESSION_ID/creditsStart
https://io.socialstream.ninja/SESSION_ID/creditsPreview
https://io.socialstream.ninja/SESSION_ID/creditsTest
https://io.socialstream.ninja/SESSION_ID/creditsReset

Replace SESSION_ID with the active Social Stream session. See Käsud ja API or the full API sandbox for more actions.

Tõrkeotsing

Session needed: use the exact Session ID from Social Stream, without the word session=.
Disconnected: confirm Social Stream is active and reopen the generated control link after changing connection settings.
Credits says no source accepted the command: reveal the ending scene, wait for its Browser Source to load, then retry.
Test works but Start is empty: Test uses built-in names. Select Background collection before the stream and confirm normal chat sources are capturing.
Featured Chat button has no visible effect: confirm the Streaming Chat Dock and featured overlay use the same session and are loaded.