Explanation of how configuration works?

Nah you can do it now, that trello card is about storing the configuration in question twitch side.

You can store the configuration you want in your EBS, provide a form in a config panel that collects SteamID and store wthat with the channel ID.

When you have both then you tell Twitch Extension API all is good.

For example:

Results in:

So Casters goes to config, which Posts back to your EBS.

Then you do use:

And call:

PUT https://api.twitch.tv/extensions///required_configuration?channel_id=

Using the example

curl -H 'Authorization: Bearer eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJleHAiOjE1MDIyOTg3ODksInVzZXJfaWQiOiIyNzQxOTAxMSIsInJvbGUiOiJleHRlcm5hbCJ9.sKjspl1jw0XGcpjF8vo2IcS2dQLQU_rSsmRCnrohCP4' \
-H 'Client-Id: pxifeyz7vxk9v6yb202nq4cwsnsp1t' \
-H 'Content-Type: application/json' \
-d '{"required_configuration": "hassteam"}' \
-X PUT https://api.twitch.tv/extensions/pxifeyz7vxk9v6yb202nq4cwsnsp1t/0.0.1/required_configuration?channel_id=27419011

So in summary:

  • You configure your extension to have “hassteam” as the required configuration
  • Caster installs your Extension
  • Caster is told to go to configuration page
  • Caster enters SteamID, which posts to your EBS/backend server
  • Backend Stores SteamID and ChannelID
  • Backend makes the PUT request with the string “hassteam”
  • Caster can now add you panel to panels/video
1 Like