StreamElements Settings

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 → StreamElements is where StreamElements is given its JWT token so donations reach the app. The page holds the token and a badge saying whether StreamElements has confirmed the connection.

How to set it up

1. StreamElements 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 StreamElements 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 StreamElements Settings, with "Configure StreamElements integration to receive donation notifications." under it.
4. Press Open StreamElements account. Your ordinary browser opens streamelements.com at the channels page. The hint spells out the route: "The token lives in your StreamElements account: account icon → channel name → enable "Show secrets" on the channel row → copy the JWT."
5. Copy that token and paste it into StreamElements JWT Token. The field hides what you type; while empty it prompts "Enter JWT Token (available in StreamElements Channel 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 JWT 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 StreamElements refused the JWT several times in a row), Sign-in required (the JWT 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 StreamElements confirmed the connection, not merely that a token is stored. A JWT that was never accepted, the wrong one pasted, shows Sign-in required straight away; an expired or revoked one gets there through the pauses described below. There is nothing to sign in to here: copy a fresh token and save it over the old one.

A refusal is not taken as final at once. If StreamElements has accepted this JWT 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 StreamElements has not yet accepted the JWT since the app started or the settings were saved. Even then the JWT is tried again every five minutes. A JWT that StreamElements has never accepted asks for a replacement at once.

What arrives from StreamElements

• Tips only. Each tip arrives as an ordinary donation, so alerts, goals, the auction and voice over pick it up. Everything else StreamElements reports, such as follows, subscriptions, cheers or merch, is ignored here. Follows, subscriptions and cheers reach the app from the platform connections under Connections → Channels, and a second copy would count them twice.
• Test alerts are not tips. The app listens for real tips on your channel, and a test fired from the StreamElements overlay editor does not reach it. Check the connection by the badge on this page, and the look of an alert by Play on the Test tab of the alert editor.

What it cannot do

• The token cannot be read back out of the app: the field shows nothing and has no reveal control.
• There is no browser sign-in — the JWT is carried across by hand. The button only opens the StreamElements page, it fetches nothing.
• The account name is not typed in. StreamElements reports it, together with the channel avatar, right after it accepts the JWT, so no donation is needed. If that one request fails, the card in the list reads "Account name appears after the first donation", but for StreamElements a donation does not bring the name: the next accepted connection does, for example after restarting the app.
• There is no separate "accept donations" switch on this page.
• Disconnecting and Remove connection (the bin icon) are on the StreamElements card under Connections → Monetization, not here.
• No donations, amounts or history are shown — this page is only about access.