musixmatch / musixmatch-sdk Goto Github PK

Just something simple showcasing the SDK that people could build off of.

Sure, this may seem redundant to say, but it's been 6 years since the last commit and obviously parts of the API have changed since then. There are lots of new API paths, such as track.lyrics.mood.get, track.richsync.get or music.genres.get, which are documented on the website but not in this repository's schema. Half of the defined properties are missing descriptions. Some example requests (like album.tracks.get?album_id=13750844&page=1&page_size=2) return 404 status codes because the referenced ID has become invalid.

I'm certain Musixmatch is getting API calls every single day, be it from individual hobbyists or from entire companies like Spotify. Yet the official GitHub repo, which is linked on the website as the official SDK, hasn't been maintained for several years. In fact, @musixmatch has last seen activity in 2016. There are open issues and pull requests posted back in 2018 without a single developer reply. Because of the state of this repository and the Swagger schema files it's impossible to generate an API client without writing the majority completely from scratch. Like, I get why companies don't pay much attention to the open source side of things, but if there's an up to date version of the Swagger schema, a quick commit and push doesn't take a minute and would be very much appreciated.

It'd be great to at least get information on why there's no longer any development on the public SDK. I'm assuming @loretoparisi could answer that?

Hi,
I'm developing a webpack project and I would like to be able to integrate Musixmatch Api. Can you tell me the right procedure or at least explain how to add it simply as a library in my index?

Thanks and regards.

Hi, I would like to use the MusixMatch SDK for Android, however the "dist/android-client-generated.zip" is missing from the "dist" folder. What should I do to use MusixMatch in my Android project?

The link for the playground in the readme is leading to a 503 page