Overview
VMSC connects to StreamElements using the Socket.IO Realtime API, a persistent WebSocket-based connection that delivers stream events in real-time. Authentication is handled through a JWT Token that you copy from your StreamElements dashboard.
Like Streamlabs, StreamElements acts as an event aggregator — it collects events from all platforms connected to your StreamElements account and delivers them through a single unified connection.
Prerequisites
- A StreamElements account with at least one platform connected
- Access to your StreamElements dashboard to retrieve your JWT Token
- VMSC installed and running on your machine
Getting Your JWT Token
The JWT Token is a long-lived authentication token that allows VMSC to connect to the StreamElements Realtime API. To find it:
- Log in to your StreamElements Dashboard at streamelements.com/dashboard
- Click your profile icon in the top-right corner and go to Account Settings
- Navigate to the Channels tab
- Click "Show Secrets" to reveal hidden tokens
- Locate the JWT Token field and copy it to your clipboard
Your JWT Token grants access to your StreamElements account data. Do not share it publicly, include it in screenshots, or paste it anywhere other than VMSC's token field. If you believe your token has been compromised, regenerate it from the StreamElements dashboard.
Step-by-Step Connection
- Open VMSC and navigate to the Sources panel from the sidebar
- Locate the StreamElements source card and click it to expand the settings
- Paste your JWT Token into the token input field
- Click Connect
- VMSC establishes a Socket.IO connection to the StreamElements Realtime API
- The StreamElements status card on the dashboard updates to show Connected
The connection authenticates and begins receiving events within seconds.
Auto-Connect on Launch
After your initial setup, VMSC stores your JWT Token securely and automatically reconnects to StreamElements every time you launch the application. The connection re-establishes itself without any manual steps.
JWT Tokens from StreamElements are long-lived and do not expire under normal circumstances. If the token stops working, you may need to regenerate it from the StreamElements dashboard and update it in VMSC.
Supported Events
VMSC captures the following event types from the StreamElements Realtime API:
| Event | Description | Key Data |
|---|---|---|
| Tip / Donation | A viewer sends a monetary tip through StreamElements | Username, amount, currency, message |
| Follow | A user follows your channel | Username, timestamp |
| Subscriber | A user subscribes or resubscribes | Username, tier, months, message |
| Cheer | A viewer cheers with Bits | Username, amount, message |
| Raid | Another broadcaster raids your channel | Raider username, viewer count |
| Host | Another channel hosts your stream | Host username, viewer count |
| Merch | A viewer purchases merchandise through the StreamElements store | Username, item name, amount |
| Redemption | A viewer redeems a StreamElements store item or loyalty reward | Username, item name, cost |
| Super Chat | A YouTube Super Chat (forwarded through StreamElements) | Username, amount, currency, message |
| Community Gift Purchase | A viewer purchases community gift subscriptions | Gifter username, gift count, tier |
Cross-Platform Aggregation
StreamElements aggregates events from all platforms connected to your account, similar to Streamlabs. If you have Twitch, YouTube, or other platforms linked, events from all of them will flow through this single connection.
If you also have Twitch or YouTube connected directly in VMSC, you may receive duplicate events from StreamElements. For example, a Twitch follow might appear from both the direct Twitch connection and from StreamElements. Use VMSC's rule conditions to filter by source, or choose to use only one source per event type to avoid duplication.
Dashboard Status Card
The StreamElements connection is displayed as a status card on the VMSC dashboard:
| Status | Indicator | Meaning |
|---|---|---|
| Disconnected | Gray | No active connection. Enter your JWT token and click Connect. |
| Connected | Green | Socket.IO connection is active and receiving events. |
| Reconnecting | Orange (pulsing) | Connection lost. VMSC is attempting to reconnect automatically. |
| Error | Red | Connection failed. Check your JWT token or network connection. |
Troubleshooting
Connection Refused or Authentication Error
- Verify that your JWT Token is correct — copy it fresh from the StreamElements dashboard under Account Settings > Channels > Show Secrets
- Ensure you copied the JWT Token and not the Account ID or other field
- Check your internet connection and firewall settings
No Events Received
- Confirm that you have at least one platform connected in your StreamElements account
- Test by triggering a test event from the StreamElements dashboard (Activity Feed > Test buttons)
- Some events only fire when you are live on the respective platform
Frequent Disconnections
- StreamElements Socket.IO connections can occasionally drop due to server maintenance
- VMSC automatically reconnects after a brief delay
- If disconnections persist, check your network stability or try regenerating your JWT Token
Next Steps
With StreamElements connected, you can create rules that respond to tips, follows, and other aggregated events:
- First Setup — Create your first rules and actions
- Rules & Actions — Full event type reference and configuration
- In-App Tutorial — Let V.I.T.R.O. walk you through everything