# Can One Twitch Application and Its Credentials Be Used Across Multiple Websites? **URL:** \ **Category:** API\ **Created:** [October 9, 2026, 1:11am UTC](https://discuss.dev.twitch.com/t/can-one-twitch-application-and-its-credentials-be-used-across-multiple-websites/65108 "2026-10-09T01:11:07Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![whoopsie](https://d3ovvz0v2ajtpu.cloudfront.net/user_avatar/discuss.dev.twitch.com/whoopsie/32/31938_2.png) [@whoopsie](https://discuss.dev.twitch.com/u/whoopsie)\ **Post date:** [October 9, 2026, 1:11am UTC](https://discuss.dev.twitch.com/t/can-one-twitch-application-and-its-credentials-be-used-across-multiple-websites/65108/1 "2026-10-09T01:11:07Z")
**Title:** Can One Twitch Application and Client ID Be Used Across Multiple Websites? I’m building and maintaining multiple independently branded streamer websites for clients. Each site uses Cloudflare Functions to fetch public Twitch stream status. 1. Can one Twitch application, Client ID, and Client Secret serve multiple independently branded websites, or must each website have its own application and credentials? If separate applications are required, must each have a unique Client Secret? 2. Would using a shared backend/API Worker or putting the websites under one root domain with creator subdomains change the answer? 3. Is displaying public Twitch API data (such as live status) on websites I build and host for clients permitted under the Developer Agreement? I want to confirm the compliant architecture before expanding. ---
**Author:** ![BarryCarlyon](https://d3ovvz0v2ajtpu.cloudfront.net/user_avatar/discuss.dev.twitch.com/barrycarlyon/32/253_2.png) [@BarryCarlyon](https://discuss.dev.twitch.com/u/BarryCarlyon)\ **Post date:** [October 9, 2026, 1:21am UTC](https://discuss.dev.twitch.com/t/can-one-twitch-application-and-its-credentials-be-used-across-multiple-websites/65108/2 "2026-10-09T01:21:37Z")
> [@whoopsie](#): > > 1. Can one Twitch application, Client ID, and Client Secret serve multiple independently branded websites, or must each website have its own application and credentials? If separate applications are required, must each have a unique Client Secret? Yes you could use one set of keys but rate limits are a thing. I would seperate them. Personally here I would probably had the streamer enter their own clientID/secret into the site and they can own the integration for their site. > [@whoopsie](#): > > If separate applications are required, must each have a unique Client Secret? Each application/ClientID has a unqiue secret… The keys (cid and secret) and unique… Like any set of oAuth keys used to generate tokens for any site/provider? > [@whoopsie](#): > > 1. Would using a shared backend/API Worker or putting the websites under one root domain with creator subdomains change the answer? Due to afor mentioned rate limits… No change on answer. But if all you are doing is live status, eventsub is a thing to consider. > [@whoopsie](#): > > 1. Is displaying public Twitch API data (such as live status) on websites I build and host for clients permitted under the Developer Agreement? I would read the agreement and decide for yourself if what you intend to do is compliant and/or consult a legal professional. But showing live status is basic public information right? TLDR: Yes, should you? I wouldn’t. ---
**Author:** ![whoopsie](https://d3ovvz0v2ajtpu.cloudfront.net/user_avatar/discuss.dev.twitch.com/whoopsie/32/31938_2.png) [@whoopsie](https://discuss.dev.twitch.com/u/whoopsie)\ **Post date:** [October 9, 2026, 1:42am UTC](https://discuss.dev.twitch.com/t/can-one-twitch-application-and-its-credentials-be-used-across-multiple-websites/65108/3 "2026-10-09T01:42:56Z")
Thanks, this is really helpful! I’ll keep the applications separate for now. One more question: Is there any limit or restriction on how many Twitch applications one developer account can register, assuming each application serves a legitimate, separate website and isn’t intended to bypass API rate limits? I’m planning to build more streamer websites over time, so I’d like to make sure this approach is okay as the portfolio grows. Thanks again! ---
**Author:** ![BarryCarlyon](https://d3ovvz0v2ajtpu.cloudfront.net/user_avatar/discuss.dev.twitch.com/barrycarlyon/32/253_2.png) [@BarryCarlyon](https://discuss.dev.twitch.com/u/BarryCarlyon)\ **Post date:** [October 9, 2026, 3:02am UTC](https://discuss.dev.twitch.com/t/can-one-twitch-application-and-its-credentials-be-used-across-multiple-websites/65108/4 "2026-10-09T03:02:47Z")
no limit to my knowledge as long as compliant with the developer agreement