I would like to suggest an improvement to Deezer's <playlist/tracks> endpoint (https://developers.deezer.com/api/playlist/tracks): it would be interesting to return album's genre data on this method in order to avoid the necessity of doing another request for each track/album to retrieve these information, turning the query quota limitation difficult for developers to deal with in cases like mine where I want to give to Deezer's user some statistics about the most popular genres on your playlists and listening history. Currently, this is the album data returned on this endpoint: object containing : id, title, cover, cover_small, cover_medium, cover_big, cover_xl.
+10Hello
https://developers.deezer.com/api
Thanks!
Hey
Thanks
Hi,
I’m currently integrating Deezer with my app and have come across some roadblocks due to the current API’s design.
Certain resources’ attributes availability vary depending on the context they are called. For example, if you make a request to retrieve tracks from a playlist, the tracks don’t include all attributes that you get when you make a request to `/track/<id>`, these are attributes like:
- isrc
- disc_number
- available_countries
- [etc]
This makes it difficult when your app needs information from a related resource (i.e. playlist track) that’s not available in the response, forcing you to make extra API requests (not good for both parties).
It’d be great if we could have a param that’d allow us to control which fields to include in a response, something like:
`/playlist/<id>?fields=id,name,track.id,track.title,track.disc_number,album.name`
Thank you.
No comments whatsoever from community managers nor devs. This is pretty sad. At the end of the day you guys are the ones that end up losing customers - imagine having more tools out there allowing people to migrate X to Deezer?
I give up supporting Deezer on my app.
Reply
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.