# Public Client Device Code Flow – Redirect URI required

**URL:** <https://discuss.dev.twitch.com/t/public-client-device-code-flow-redirect-uri-required/65141>\
**Category:** API\
**Created:** [October 16, 2026, 9:52am UTC](https://discuss.dev.twitch.com/t/public-client-device-code-flow-redirect-uri-required/65141 "2026-10-16T09:52:02Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![hhvilt](https://d3ovvz0v2ajtpu.cloudfront.net/user_avatar/discuss.dev.twitch.com/hhvilt/32/31942_2.png) [@hhvilt](https://discuss.dev.twitch.com/u/hhvilt)\
**Post date:** [October 16, 2026, 9:52am UTC](https://discuss.dev.twitch.com/t/public-client-device-code-flow-redirect-uri-required/65141/1 "2026-10-16T09:52:02Z")

</div>

Hello! I’m developing an Android app called hhvilt Studio.

I want to register a Public Client using Twitch OAuth Device Code Flow. However, the Developer Console requires an HTTPS OAuth Redirect URL, even though Device Code Flow doesn’t use a redirect URI.

What is the officially supported way to register a Public Client for Device Code Flow without setting up an HTTPS callback?

Thanks!

---

<div class="post-metadata">

**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 16, 2026, 9:55am UTC](https://discuss.dev.twitch.com/t/public-client-device-code-flow-redirect-uri-required/65141/2 "2026-10-16T09:55:24Z")

</div>

use the (iirc default) value of `http://localhost`

It’s noted that if a user when device code flowing, hits “cancel/deny access” they will/may be rerouted to the redirect URI.

So it might be adviased to redirect to a page on the website that the user got your tool from which then says “oh you decided not to allow the connection”

So for example my code example of the device code flow (when I’m developing/testing it) uses `https://barrycarlyon.github.io/twitch_misc/` and there I have this [twitch\_misc/index.html at gh-pages · BarryCarlyon/twitch\_misc · GitHub](https://github.com/BarryCarlyon/twitch_misc/blob/gh-pages/index.html#L69) to catch that “exit” route to advise the user what happened, that being they declined the connection (and/or handle other error states).

So it would be benficial to use a “real page” connected to your tool/product for catch error/fall thru states.