in_reply_to_status_id is populated when a tweet is a reply to another tweet.
The status_id in this context refers to the tweet being replied to. For this
field to be populated, the "reply tweet" also must begin with the @username
of the user being replied to.

A @reply in XML:
http://gist.github.com/620548#file_reply.xml

in_reply_to_user_id indicates the @user being mentioned by primary key "id",
which never changes for the member though the screen name might.
in_reply_to_user_id may be populated on a @mention (which does not have a
referenced tweet in in_reply_to_status_id).

A @mention in XML:
http://gist.github.com/620548#file_mention.xml

And while Thomas is right that it's great to explore with an API console,
I'd personally recommend that API console at
http://app.apigee.com/console/twitter instead of the one we provide on
dev.twitter.com.

Taylor


On Mon, Oct 11, 2010 at 6:51 AM, Thomas Mango <tsma...@gmail.com> wrote:

> Hey, Colin. An easy way to test API calls and see their response is by
> using the console (you need an app registered):
> http://dev.twitter.com/console
>
> Or by getting a copy of twurl to use locally:
> http://github.com/marcel/twurl
>
>
> Colin Howe wrote:
>
>> Hi,
>>
>> I can't find any documentation on the response format for anything
>> that returns tweets. E.g.
>> http://dev.twitter.com/doc/get/statuses/mentions
>>
>> Is there any documentation of what the response looks like and what
>> each field means?
>>
>>
>> Specifically, I'm looking for information on when in_reply_to_[status|
>> user]_id are populated and what they are populated with.
>>
>>
>> Thanks,
>> Colin
>>
>>
>
> --
> Thomas Mango
> tsma...@gmail.com
>
>
>
> --
> 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

Reply via email to