MuseScore API changes?
Hello, have there recently been any MuseScore API changes? My Telegram bot for MuseScore @musescorebot , which I made a while ago and posted in this thread does not work anymore. Could there be any API changes or do those API tokens expire after some time?
Comments
Normally the API still works and didn't change. What type of issue do you have with your bot?
There are no changes on the API, nor do tokens expire after some time. Please report which issues you are having currently via support@musescore.com or if you want by leaving a comment in this thread.
In reply to There are no changes on the by Thomas
Thanks for the answer. My problem is that the bot suddenly does not show inline results for musescore queries anymore. However, since you say that you did not change anything, it will probably be a problem on the Telegram side (though I don't see any API changes there either for methods that I use). Will probably look into it later. Again thanks for your help. :)
In reply to There are no changes on the by Thomas
Alright, I think that the problem is still on the MuseScore site...
Is it correct that I get a 404 error at curl 'http://api.musescore.com/services/rest/score?oauth_consumer_key=your_co…' ?
In reply to Alright, I think that the by Piano Ninja
According to http://developers.musescore.com/#/search-scores the last part of your URL should be score.xml: which without a consumer key gives a 403; so existing but not allowed (as expected)
In reply to According to by jeetee
Jeetee is right: you are missing either .xml or .json. And you need to a consumer key. If you don't have any yet, please email api at musescore dot com.
In reply to According to by jeetee
Ok, I still don't get it. If I literally copy the example from the documentation:
http://api.musescore.com/services/rest/score.xml&oauth_consumer_key=you…
And replace your_consumer_key with my consumer key, I get a 404 error. I also tried moving the score.xml to the end. I also tried using score.json, but none works.
Any idea what I am doing wrong?
In reply to Ok, I still don't get it. If by Piano Ninja
I fixed it now by myself.
The API was in fact changed. First of all the example URL on the documentation is wrong, you have to use http://api.musescore.com/services/rest/score.xml?oauth_consumer_key=you… instead of http://api.musescore.com/services/rest/score.xml&oauth_consumer_key=you…
I think this should be updated in the examples section.
Second, the json that is returned, if score.json is specified, was slightly changed too. The old json is now in a new member 'score'. So I had to first change to the member 'score' of the returned json, and could then work with the Json as I did before the change.
So with these changes implemented, the musescorebot is now working again :)
In reply to I fixed it now by myself. The by Piano Ninja
Thanks for sharing your findings. Looks like the docs contain a typo which wasn't reported before so we will fix this. As for the change with the JSON output, if this did indeed change, we will fix this as this is not intended. Keeping you posted.
In reply to I fixed it now by myself. The by Piano Ninja
@Piano Ninja The json API issue and the documentation problem are fixed. I assume your app will be broken again, so sorry about this.
In reply to @Piano Ninja The json API by Thomas
Thanks for the notice, I implemented the change and the bot is working again. :)