With as often as this comes up, it's obvious that we aren't communicating this clearly and the historical aspect of this isn't obvious:
An @reply requires that it begins with the @username of the user being replied to. The in_reply_to_status_id field is not enough to associate the tweets as a reply -- the username must also be present. Also: When using a POST method, don't include your fields/parameters on the query string. Instead, put them in the POST body. You may find someday that passing such parameters on the query string just stops working. Taylor On Thu, Oct 7, 2010 at 1:37 PM, Matthew <[email protected]> wrote: > Hello, > > Been working on a project that will allow users to reply to tweets. I > am having difficulty in getting the 'in_reply_to_message_id' to be > acknowledged. I have been using the latest version of Abraham's > TwitterOAuth library, also confirmed the problem through apigee. > > Example request (over POST): > > http://api.twitter.com/1/statuses/update.json?in_reply_to_status_id=26673308442&status=looks > like its not working for apigee either > > I can confirm the in_reply_to_status_id message is a message I posted > earlier. > http://api.twitter.com/1/statuses/show/26673308442.json > > > I get a response back from twitter with field populated except with > "in_reply_to_status_id" : null. > Is there currently a glitch in the twitterapi, or am I using this > function improperly? > > > Thanks in advance! > > -- > Twitter developer documentation and resources: http://dev.twitter.com/doc > API updates via Twitter: http://twitter.com/twitterapi > Issues/Enhancements Tracker: > http://code.google.com/p/twitter-api/issues/list > Change your membership to this group: > http://groups.google.com/group/twitter-development-talk > -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
