feat: Deezer updated their API

[Ectalite]

Please check existing knowledge before opening an issue

• I have checked the documentation
• I have searched through existing issues and discussions.

Describe the new functionality

Hi, after being such an headache, Deezer finally updated their API endpoint. Now it's completely free without any worry to have with API keys or else.
https://developers.deezer.com/api

I found an implementation here in typescript to get the history: https://github.com/tomheaton/deezer-stats/blob/main/src/fetchers/history.ts

I hope it will be fine to use !

I never wrote typescript, but maybe I could find time to understand the code and update it.

Configuration Example

Will you help implement it?

• I am willing to contribute code towards completing this feature
• I am willing to help test preview builds for this feature

[FoxxMD]

This is great news!

multi-scrobbler already has an implementation for Deezer and the API looks to be unchanged, from their side. I will investigate this and un-deprecate the deezer Source if everything is in working order.

[FoxxMD]

Are you sure the API was updated? Do you have a source for news on this?

On the myapps page it still says

We're not accepting new application creation at this time

and trying to access my existing app returns a 404 page. Nothing has changed AFAIK.

[Ectalite]

Yeah after checking it more deeply it didn't change, I really though there was something to do with their OAuth thing and the title saying it was "Unlimited Access, without stress, without identification".
Sorry for the false expectation...

Do you think there would be something to do with the arl cookie some tools are using to bypass OAuth requiring myapps ?

[FoxxMD]

It's possible but not something currently implemented for non-piracy related libraries. My earlier research indicated there 3 types of libraries for deezer:

• wrappers around the public API, like deezer-ts, that have no auth
  • Do not implement user/me/history endpoint for obvious reasons
• piracy-related wrappers that use ARL cookie to download higher-bitrate tracks from scraped internal endpoints
  • Do not implement user/me/history endpoint because they don't use the public API and have no use-case for it
• old libraries that implement oauth
  • can't be used anymore before the api is still deprecated/restricted
  • deezer-stats falls under this category. It is using oauth and must have an app from before deezer locked it down.

None of these options give me a path forward with multi-scrobbler and I don't want to reverse engineer and maintain a fork of the piracy-related libraries given I don't even know if they will work.

Additionally, since I don't have Deezer Premium I can't play full tracks so my history is never populated which means I can't test it anyways.

I encourage you to fork one of these ARL-related libraries and see if you can get it to work. If someone else was maintaining the library that multi-scrobbler would use I would consider using it for Deezer source.