Title: consumer_key no longer supported?

Issue found of: September 20th, 2020

It looks like you have seriously overhauled the API and access to it and and I'm unclear if apps like gPodder (a podcast client) are still supported in this model since an OAuth token is inherently bound to a user and not an application.

At the moment all API requests that I attempt to run return 401, from a quick look at the API docs it also looks like they are to your old API, example:

https://api.soundcloud.com/users.json?q=%22Medic%20Mindset%22&consumer_key=[GPODDER_KEY]

For a while it was actually returning real data and 401s at random (I assume depending on which server it was being load-balanced to) but now it seems to always be 401.

So can things still work by moving the consumer_key to an authentication header or is this no longer supported in any way?
Is the SC API supposed to only be accessed by registered SC users from now on?

Thanks!