I am testing the Music API and I am hitting walls every single moment when I try to do something that is DOCUMENTED but doesn't work/exists.
Documentation says, /v1/catalog/us/artists/{ID}/view/{view}/ NEVER returns 404, while I am getting 404 for even content I know it's available on Apple Music.
e.g
/v1/catalog/us/artists/1487603897/view/appears-on-albums/
results 404 while they are appearing on an album FRIGID ******* of Nosphere artist.
So when I request for appears-on or featured albums it shoud appear as a result, but I get 404.
It's here so it should appear: https://music.apple.com/us/album/frigid-silence/1791001624?i=1791001626
I found NO WAY to get that album for this artist using the API, which is very frustrating and annoying.
Similarly if I try this:
/v1/catalog/us/artists/{ID}?views=>appears-on-albums it will result an EMPTY array for the data property
Also the documentation is unclear about the several limitation max values, many parameters (e.g. include parameters are unknown ) we can't tell what value can we use.
Is Apple Music Api unreliable or I just don't understand something?! I don't even understand why I have to do 4 different requests to get an artists all albums (full, single, featured, appears-on)... this should be MUCH more easier to do it one single request (with pagination).
We are working on a long-term major investment in music startup and trying to move from Spotify API (due to recent changes and limitations) and finding a better alternative. Based on the docs Apple Music API seemed the most promising one, but now we are testing it we are very disappointed so far.
So should we trust in this or should we forget about Apple Music API?