410 gone when requesting private `/api` API namespace with 3rd party client ID

My point was that Twitch could make these endpoints not work with our client IDs, yet we’ve been able to use these endpoints with out client IDs for years. Our client IDs do work with these endpoints which suggests that, despite what you claim, Twitch does support us using them.