The Muxy Developer Hub

Welcome to the Muxy developer hub. You'll find comprehensive guides and documentation to help you start working with Muxy as quickly as possible, as well as support if you get stuck.

What is the Muxy SDK?

MEDKit is a JavaScript library for building viewer-facing extensions on Twitch. It uses the MEDKit REST API , which you can also use directly.

MEDKit is part of an SDK designed to make building a Twitch extension easy.

The complete SDK also includes the GameLink API that lets a Twitch developer interact directly with the Muxy server, to integrate your game or other broadcast content with viewer data in real time.

For server-to-server interactions, you can communicate directly over HTTP using the GameLink API and WebSocket Protocol.

APIs are available in C, C++, C#/Unity, and as an Unreal plugin.

What do I use it for?

Game Developers

  • Increase the length of time your game is played on Twitch.
  • Increase game sales.
  • Engage and monetize your viewers.

Extension Writers

  • Create streamer engagement tools.
  • Offer new revenue options for streamers.
  • Generate money-making opportunities.

Streamers

  • Find new ways to monetize your audience.
  • Promote viewer engagement.
  • Create quizzes and viewer events with reward options.

Muxy features and services for Twitch Extensions

Extension state

The Muxy server maintains persistent state information about Twitch extensions, their broadcasters, and their viewers, and makes it available to clients in real time -- at a high level through the MEDKit JavaScript API, and directly through the MEDKit REST API.

The full set of functionality is also available at a lower level through the GameLink API and WebSocket Protocol.

Scaling up

The Muxy SDK provides data aggregation tools to help you create viewer engagement activities in a large user base.

The Muxy SDK provides services for interacting with large numbers of viewers through various forms of data aggregation, from simple accumulation to a polling service, a ranking service for viewer input, and a trivia-quiz service.

Access Control and Messaging

Access to functionality is gated through user roles. An extension user can be a viewer, a broadcaster, or an admin -- that is, a user with administrative privilege who can set policies and configuration.

A messaging protocol allows extensions to communicate. A client can broadcast messages to all or some viewers, and also publish and subscribe to message threads. The messaging system allows private backchannel communication for coordinating activity among extension instances across channels.