Posted on 20,Dec |
Posted by cedric UPDATE: that’s it! Migration done: Moodstocks API now runs the latest Moodstocks Cloud version (more details on the underlying architecture soon!).
Dear API users,
Please note we’ve scheduled a maintenance update of our Moodstocks API platform starting today (Dec. 20th) around 10:30 Paris time. It should last around 2 hours. Behind the scenes we’ll migrate on the latest Moodstocks Cloud release. During this migration our mobile applications (MContacts, MNotes and MShopper), web portal and REST services will be down. We’ll keep you informed as soon as the service re-operates normally.
Comments
By kexik
507 days ago
I can’t get recognition working.
It looks like API URLs was changed?!
Why didn’t you inform users about it?
Previously it was:
http://api.moodstocks.com/items/recognize
And now:
http://api.moodstocks.com/v1/recognize ??
I got adding/removing via PUT/DELETE working, but recognition is not working!!
For adding/removing items I now use this URL:
http://api.moodstocks.com/v1/item/ID
Any idea why recognition is not working after changing URL?
Thanks in advance.
By cedric
507 days ago
Hi Kexik,
First of all thank you for your feedbacks.
We’re very sorry here at Moodstocks that you’ve experienced some issues with the API. These issues are probably related to the above migration and/or the downtime we’ve experienced on Dec 25th due to Amazon EC2 Ireland issues (a new blog post on this topic soon).
Regarding the API endpoint, we’ve indeed introduced API versioning as the new official routes. For more details, feel free to refer to our official doc page that has been updated after the migration: https://github.com/Moodstocks/moodstocks-api-kits/wiki/Developer-documentation.
With a versioned API, it will be easier and smoother in the future to release major API changes while still make sure older clients work.
That being said, please note that we’ve *still maintained the old routes* for backward compatibility. In other words sending requests to /items/recognize (via GET and image_url or POST and image_file) still work. If the recognition doesn’t work, then it is related to another issue(s).
I’ll give you asap more details related to your very own API account and data through direct email.
By kexik
507 days ago
Hi Cedric,
thanks for the quick response! Looks like I am getting a Bad request response from the server using the old route (and probably using the new one too). That’s strange, because the app worked before your migration and stopped working after it. It seems that something was changed. I will take a look to the new docs and try to debug app-server communication.
By cedric
507 days ago
@kexik: you’re welcome! I’ve just sent you a direct email with some more details that’ll help us investigate what’s the trouble (if any).
By cedric
507 days ago
Update: @kexik as mentioned via private email, and since it could potentially help other API users, please note that your problem is related to a bug in ASIHTTPRequest (popular Objective-C HTTP library).
We’ve already identified this bug, contacted ASIHTTPRequest’s author via Twitter and also opened a pull request: https://github.com/pokeb/asi-http-request/pull/120. Feel free to refer to this pull request for more technical details.
In the meanwhile we’ve also applied this patch to our official Moodstocks iPhone SDK (https://github.com/Moodstocks/moodstocks-iphone-sdk) – that’s why we strongly encourage our API users to work with it as far as their iPhone apps are concerned. Since the SDK provides a high-level abstraction, it makes easy to integrate our solution without getting your hands dirty with such technical stuff!