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

Btw, it’s not just /api/channels/CHANNEL/access_token.json, but the entire private /api namespace which is affected by this change.

Since Twitch does not provide every feature on /kraken or /helix, many app developers have to use certain /api endpoints. As I’ve said, simply using the client-id of Twitch’s website doesn’t sound like a proper solution and more like abusing the system.

I would appreciate if we could get a statement in regards to this change, as it is causing massive issues today for 3rd party app developers like me. Thank you.