multi-scrobbler/config/mixcloud.json.example
Anand Hegde 6fa5ea47a0 feat(mixcloud): support OAuth apps and private/pro histories
Add optional clientId/clientSecret config for a Mixcloud application.
When both are defined the source runs the OAuth authorization flow
(redirecting through /api/mixcloud/callback), persists the received
access token next to the config like the spotify source, and reads
listens from /me/listens/ -- which includes the private and pro
listening history the public endpoint does not expose. The username is
discovered from the authorized user's profile.

With only a username the source behaves exactly as before, so existing
configs keep working unchanged.
2026-10-14 13:41:12 +00:00

23 lines
736 B
JSON

[
{
"id": "myMixcloud",
"name": "MyMixcloud",
"enable": true,
"clients": [],
"data": {
// Option 1: monitor a user's public listening history (no authentication needed)
"username": "MyUsername",
// Option 2: authenticate with a Mixcloud application to monitor your own
// listening history, including private (pro account) history.
// Create an application at https://www.mixcloud.com/developers/ to get
// these, then use the Authorize button on the source to complete sign-in.
// When used, `username` is optional.
// "clientId": "...",
// "clientSecret": "...",
// optional: polling interval in seconds (default 60)
"interval": 60
}
}
]