#Qaiku-api

For both http://www.qaiku.com/api/statuses/upd... and http://www.qaiku.com/api/statuses/upd... I get:

HTTP/1.0 404 Not Found
Action update not found (GET /api/statuses/update.json)

(ping @bergie / @eholmila)

ok, it seems you just get a 404 if your request isn't perfect. Not exactly intuitive for developers.

@dsample define "perfect", what conditions cause it?

well, one example, if you just want to check the end-point exists you might try going there in a browser and expect an error of some kind telling you that you need to authenticate or that some parameters are missing. For the Qaiku API it just gives a 404 error.

This is the same if you get some of the parameters wrong (my script wasn't sending the POST arguments properly), but all I could see was a 404 error, rather than being told that I hadn't provided some information (like Twitter and other services do).

@dsample: you'll have to show later tonight what I'm doing wrong with the thingamabob, can't make it work with ping.fm either :-(

and true, atleast with ping.fm I get

"user.post This API only accepts POST requests."

while qaiku just gives

"Action update not found (GET /api/statuses/update.json) Midgard CMS power since 1999. Perfect software." (irony isn't lost on me ;-D)

@myrtti slightly updated script from the one you have. I've got my new version working with Qaiku, Jaiku, Twitter and Identi.ca.

It won't work with Ping.fm yet, since they're a lot more strict that apps must use OAuth.

This is interesting as the API component does set correct HTTP status codes and messages for different situations. I suspect something in Qaiku catches my exceptions and throws them onwards as 404s instead. I'll check that when @tepheikk returns from Korea.

wohey, works!

For more comprehensive checking, here is the list of potential error codes Qaiku API can send when posting to statuses/update.json:

General Midgard and authentication stuff that applies to all API:

• Other HTTP method than POST attempted: 405 GET not allowed
• Other HTTP method than POST attempted (fallback mode): 404 Action X not found
• Invalid API key: 500 Invalid API key
• Internal failure to do API key auth: 500 API key authentication failed
• API usage disabled by user: 405 User has disabled API usage, enable it in API settings

• status not provided: Error 400 Missing status message
• Posting to channel where user isn't allowed to: 401 Not allowed to post to channel X
• Posting to channel that doesn't exist: 404 Channel X not found
• Message in_reply_to_status_id can't be found: 404 Status message X not found
• Trying to repy to a different channel than thread parent: 400 Cannot reply to different channel than original message
• New Qaiku is longer than 140 and not a reply: 400 Status messages must be 140 characters or shorter