{"id":52198,"date":"2026-04-03T11:06:50","date_gmt":"2026-04-03T11:06:50","guid":{"rendered":"https:\/\/barrycarlyon.co.uk\/wordpress\/?p=52198"},"modified":"2026-04-03T11:22:00","modified_gmt":"2026-04-03T11:22:00","slug":"twitch-app-access-tokens-yay-announcements","status":"publish","type":"post","link":"https:\/\/barrycarlyon.co.uk\/wordpress\/2026\/04\/03\/twitch-app-access-tokens-yay-announcements\/","title":{"rendered":"Twitch App Access Tokens – YAY ANNOUNCEMENTS!"},"content":{"rendered":"\n

You may have read the previous post about Twitch App Access Tokens doing more<\/a>, and my sadness about Send Chat Announcement<\/a> not being supported, well yesterday that was rolled out!<\/p>\n\n\n\n

\"A<\/figure>\n\n\n\n

But Wait, theres MORE<\/h2>\n\n\n\n

Yes, there is more to the MORE!<\/p>\n\n\n\n

Send Chat Announcement<\/a> includes the same control\/ability that Send Chat Message<\/a> has, the ability to control if<\/em> that Announcement goes to all Channels if the channel is in shared chat<\/a> mode, with the default being true\/send only to home channel.<\/p>\n\n\n\n

So broadly this means you can run a Twitch chat bot off JUST the App Access token<\/a>, as most functions a chat bot will do day to day in the primary function thread can use the Token.<\/p>\n\n\n\n

Which has the added benefit of not having to juggle tokens, user refresh tokens, saving those, as to get a new App Access Token, it’s just load ClientID and Secret from env<\/code> and go get a new token! And of course App Access Tokens has a longer life time of around 60 days or so, which means less refresh operations overall!<\/p>\n\n\n\n

To also note there are no additional permission\/scope changes here! You should be all good to go if already using conduits and were user token-ing to send announcements.<\/p>\n\n\n\n

So What Else?<\/h2>\n\n\n\n

The Change Log<\/a> offered the following:<\/p>\n\n\n\n