Hello @nataliaspeck, Could you please send this to our developpers directly here? 

https://developers.deezer.com/api

Thanks! 

Hey @nataliaspeck , I’m having a similar issue and was wondering if you followed up with Deezer’s dev team and heard back from them?

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
• eetc]

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.

Was my topic merged here, @yula?

No indication of a merge ...

Hi,
Need genre information too for artist endpoint.

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.