LiveSticky

Setup Guide

How to install and connect LiveSticky in under 5 minutes.

LiveSticky operates entirely within the Reddit Developer Platform, meaning there is no external server to manage, no code to write, and no bot account to invite. However, to pull real-time live data from platforms like Twitch, YouTube, and Kick, you must provide your own API credentials.

Step 1: Install & basic config

First, install the app on your subreddit.

  1. 1
    Navigate to the LiveSticky App Page and click Install.
  2. 2
    Open your subreddit, go to Mod ToolsAppslive-stickySettings.
  3. 3
    Fill out the basic settings such as the Twitch Channel Name, YouTube Channel Name, or Kick Channel Name.

Step 2: Platform API setup

Select your streaming platform below to see the specific instructions for generating your API keys.

If you want LiveSticky to detect when you are live on Twitch, you must provide a Client ID and Secret.

  1. 1
    Go to the Twitch Developer Console and log in.
  2. 2
    Click Register Your Application.
  3. 3
    Set Name to anything (e.g. MySubreddit LiveSticky), set OAuth Redirect URLs to http://localhost, and select Website Integration as the category. Click Create.
  4. 4
    Click Manage on your new app. Copy the Client ID and generate a new Client Secret. Paste both into the LiveSticky app settings.

To detect live broadcasts on YouTube, you must generate a YouTube Data API Key.

  1. 1
  2. 2
    Create a new project (or use an existing one).
  3. 3
    In the sidebar, go to APIs & ServicesLibrary. Search for YouTube Data API v3 and click Enable.
  4. 4
    Go to APIs & ServicesCredentials. Click Create CredentialsAPI Key.
  5. 5
    Google will prompt you to restrict the key. Under Select API restrictions, select YouTube Data API v3 from the dropdown and click Create.
  6. 6
    Copy the generated key and paste it into the LiveSticky app settings.

To detect live broadcasts on Kick, you need a Kick API application.

  1. 1
    Navigate to the Kick Developer portal or the developer settings in your Kick account.
  2. 2
    Generate a new Client ID and Client Secret.
  3. 3
    Paste them into the LiveSticky app settings.

Step 3: Testing it out

Once your API credentials are saved, LiveSticky will automatically start polling your channels every 2 minutes. You can also manually test your setup using the Mod Menu actions.

  1. 1
    On your subreddit homepage, click the Mod Actions (shield icon) and select Create Dashboard to spawn the interactive multistream dashboard.
  2. 2
    If any of your API keys expire or hit a quota limit, LiveSticky will automatically send a ModMail alert to your subreddit so you can fix it immediately.

Who can see your API credentials

The keys you pasted in Step 2 are stored as subreddit settings on Reddit's Developer Platform. Any moderator with access to your subreddit's app settings can open that page and read them. That is how per-subreddit settings work on Devvit and applies to every app, not just LiveSticky: an app cannot hide a setting from the moderators who are allowed to edit it.

What those keys can do if someone copies them is limited. All three are read-only credentials for public data: Twitch and Kick client credentials grant App Access Tokens that can read public stream status, metadata, and clips, and a YouTube API key can read public channel and video data. None of them can post, moderate, change your channel, or reach anything private. The realistic risk is someone burning your YouTube daily quota or making requests in your app's name.

Practical advice:

  • Create the credentials on an account the whole mod team is comfortable being tied to, rather than a personal main account.
  • Treat them as shared with your current mod team, the same way you would a shared bot password.
  • Rotate them if someone leaves the team: regenerate the secret in the Twitch Developer Console, the Google Cloud Console, or the Kick developer portal, then paste the new value into Subreddit Settings.

Full outbound request disclosure lives on the External APIs page.


Configuration Reference

Looking for a complete breakdown of all settings, customizable post template flairs, dynamic placeholders (like {viewers} or {uptime}), and moderator control options? Check out the full Configuration Reference.