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

It’s unlikely Twitch are going to make a statement. It has already been said, numerous times, that if you use these undocumented endpoints you use them at your own risk as they can and will change/break.

Changes/removal of some of these undocumented endpoints were somewhat known, and if you continued to use them up until the point they changed or were removed then that was the risk you took knowing full well that it was likely to happen at some point.

If you don’t want issues like this in the future, don’t use endpoints that Twitch never intended for 3rd parties to use. If that means you’ll be lacking certain pieces of functionality in your app then either accept that Twitch don’t want 3rd parties to have that functionality, or risk trying to circumvent restrictions Twitch are placing on this endpoints and further risk your apps (and potential violation of the developer agreement) future.