Ah, no - I think you still get a 200 status code (using xml anyway)
On Dec 14, 3:52 am, fastest963 <[email protected]> wrote: > Ah gotcha! so i should just just look for the 200 status code :) > Thanks! > > On Dec 12, 11:00 pm, "Damon Clinkscales" <[email protected]> wrote: > > > cURL is your friend. > > > "Bad ID": > > $ curl "http://twitter.com/statuses/show/123456.json"; > > {"request":"\/statuses\/show\/123456.json","error":"No status found > > with that ID."} > > > "Protected Update": > > $ curl "http://twitter.com/statuses/show/1054113093.json"; > > {"request":"\/statuses\/show\/1054113093.json","error":"Sorry, you are > > not authorized to see this status."} > > > "Public Update": > > $ curl "http://twitter.com/statuses/show/1052591473.json"; > > {"in_reply_to_user_id":null,"text":"\"Why do you look askance at my > > juice.\"","user":{"description":"No ideas but in > > things.","url":"http:\/\/1vy.org\/","name":"Evan","followers_count":1124,"p > > rotected":false,"profile_image_url":"http:\/\/s3.amazonaws.com\/twitter_pro > > duction\/profile_images\/66286904\/aquarium-fish-icon_normal.jpg","screen_n > > ame":"_evan","location":"Russian > > Hill, > > California","id":761613},"in_reply_to_screen_name":null,"truncated":false," > > favorited":false,"created_at":"Fri > > Dec 12 02:31:44 +0000 > > 2008","id":1052591473,"in_reply_to_status_id":null,"source":"web"} > > > -damon > > > On Fri, Dec 12, 2008 at 9:24 PM, fastest963 <[email protected]> wrote: > > > > Well, the subject says it all, but I'm requesting a ID by /statuses/ > > > show/123456.json and I was wondering what I can expect the output to > > > be if either the ID doesn't exist or if it is protected. > > > > In other words: how can I easily check to see if it returned > > > correctly? > > > > Thanks, > > > James Hartig
