Apologies for the late reply. I hope you've figured it out. If not, you can take advantage of the Playlist relationship endpoint and provide tracks as the relationship. It provides you with all the tracks. Example: https://api.music.apple.com/v1/catalog/us/playlists/pl.f4d106fed2bd41149aaacabb233eb5eb/tracks

As I mentioned, is it not possible to provide an in-app experience (and not take the user to the Apple Music app)?

"One thing to know though is that, if the curator relationship of the playlist in Apple Music API happened to point to resources of type AppleCurators and kind equal to "Genre", then you still won't be able to access it, because those resources are not yet exposed in MusicKit." Ah, I wasn't sure about the kind. Thank you for the clarification!

After looking at the response from the endpoint once again, it is very much designed to be not a list of items, rather than a few items, as it is "top" ones. I will have to rethink why I wanted them as lists.

That def makes sense. Thanks for the clarification! I just had a look at the Apple Music app, and they are also following the way you mentioned, one item at a time instead of a different list for each music item.

Yes, it does! For simplicity, I wanted to have separate arrays of songs, albums, etc., like how MusicKit has in MusicCatalogSearchResponse like albums: MusicItemCollection<Album>, songs: MusicItemCollection<Song> if that makes sense. Otherwise, there is no problem with the current implementation!

Ah yes, I am going through all the endpoints again that I forgot I raised a question regarding curator earlier. Oopsie!

Ah, if the whole section is deprecated, they should remove it or put a deprecated tag on it...

It turned out to be easier than I thought. All I had to use was MusicItemCollection without creating a custom structure!

Thank you so so much for this information! I wouldn't have figured this out at all from the documentation.

Aha, oopsie. I have been relying on MusicDataRequest right now. Do you think this change in the SDK will be locked for that iOS version and above?

It is a weird workaround, but thank you for it nonetheless!

Using this endpoint and the privileged/illegal token, you can easily get the artist images https://amp-api.music.apple.com/v1/catalog/us/artists/901863670?extend=artwork. Sigh, that the developers cannot access it using their tokens

That makes sense. Creating a third-party Apple Music client is a use-case to provide for all Apple platforms, and from what I understand, right now, watchOS and native macOS (due to engineering challenges) are not supported. I will file a ticket for this! Thank you for the response!

I can confirm that it works fine on my app. Thanks!