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

If these endpoints aren’t intended for us to use, why can we make client IDs that work with them? I could see that being a valid response if there were no way for us to use these endpoints with proper authentication, but that’s not the case. We can make client IDs for applications to use these endpoints.

As is, in order to make applications that work with Twitch fully, we have to figure out these endpoints entirely ourselves. It would be nice if these endpoints were properly documented and supported. Twitch clearly supports us using them otherwise we wouldn’t be able to use our own client IDs with them. It would just be nice to get some actual support and documentation here.