strAImer strAImer
Sign in

Streamlabs Settings

People ask this as

Installed separately: this module does not come with the app installer. Open Module Catalog → Add-ons and press Install on its card; until then the app does not have it.

What this page is

Connections → Monetization → Streamlabs is where Streamlabs is given its socket token so donations reach the app. The page holds the token and a badge saying whether Streamlabs has confirmed the connection.

How to set it up

  1. Streamlabs does not come with the app. If the card is missing from Connections → Monetization, install it first from Module Catalog → Add-ons.
  2. Press Connect Streamlabs on the card. On an already connected card the same page opens with Configure. The arrow in the top left, Back, returns to the list.
  3. The page is headed Streamlabs Settings, with "Configure Streamlabs integration to receive donation notifications." under it.
  4. Press Open Streamlabs dashboard. Your ordinary browser opens streamlabs.com at the API settings. The hint on the page says where to look: "The token lives in your Streamlabs dashboard: Settings → API Settings → API Tokens → Your Socket API Token."
  5. Copy that token and paste it into Streamlabs Socket Token. The field hides what you type; while empty it prompts "Enter Socket Token (available in Streamlabs API Settings)".
  6. Press Save Settings in the top right corner. The button reports on itself — Saving…, then Saved, or Error if the token was not stored. After a successful save the page closes itself and returns to the list of services.
  7. Saving an empty field when no token is stored yet is refused with "Please enter your Socket API token".
  8. Reopen the page to check. The field is empty on purpose — a stored token is never shown back. That it exists is said by the prompt inside the field: "Token saved — leave empty to keep it". Leaving it empty and pressing Save Settings keeps the stored token; to replace it, type the new one over.
  9. Connection Status at the top carries the badge: Disconnected (no token saved), Connecting…, Connection error (the connection dropped, or Streamlabs refused the token several times in a row), Sign-in required (the token needs replacing), or the connected state naming the account. It refreshes by itself every few seconds while the page is open.
  10. A green badge means Streamlabs confirmed the connection, not merely that a token is stored. A token Streamlabs has never accepted, the wrong one pasted, shows Sign-in required straight away. Despite the wording there is nothing to sign in to here: copy the Socket API Token again and save it over the old one.

A refusal is not taken as final at once. If Streamlabs has accepted this token before, a refusal is answered with a pause and a new connection: 5 seconds, then 10, 20 and so on, up to five minutes, and the badge turns to Connection error only from the third refusal in a row. Sign-in required shows after refusals have gone on for ten minutes, or for two to three minutes if Streamlabs has not yet accepted the token since the app started or the settings were saved. Even then the token is tried again every five minutes, so the badge turns back by itself once Streamlabs accepts it.

What arrives from Streamlabs

Donations only. Each one arrives as an ordinary donation, so alerts, goals, the auction and voice over pick it up. Follows, subscriptions, bits, merch and the other events Streamlabs also forwards are ignored here: follows, subscriptions and bits reach the app from the platform connections under Connections → Channels, and a second copy would count them twice.

What it cannot do