Also, if you're looking for tweets by a specific user, it's much better to browse their user timeline directly rather than using the Search API (which only goes back a few days):
http://dev.twitter.com/doc/get/statuses/user_timeline Example invocation: GET http://api.twitter.com/1/statuses/user_timeline.json?include_entities=true&include_rts=true&count=100&screen_name=twitterapi @episod <http://twitter.com/episod> - Taylor Singletary On Mon, May 16, 2011 at 7:53 AM, Damon Parker <[email protected]> wrote: > > This is from a PHP app I built using a the the twitter-async class: > $tweet = > $twob->get('/statuses/show/'.$tw_id.'.json?include_entities=true'); > > Whatever language you are using, the url you are looking for is: > > '/statuses/show/'.$tw_id.'.json?include_entities=true' > > > Documentation: > http://dev.twitter.com/doc/get/statuses/show/:id > > > > -- > damonp > > On Sunday, May 15, 2011 at 8:30 PM, MyGradThesis wrote: > > Hello Twitterati!!! > > I'm writing a Twitter feed tool to help me complete my grad thesis > (would be happy to share it, this is non-commercial) and the one > problem I have now is how do I get a single, historical status > returned to me in json format? If someone could reply with the get > syntax for getting a single status that would be great. I found a get > command for direct messages, but these are just plain old statuses > that I need, so the direct message get does not work for me (i.e. GET / > 1/direct_messages/show/:id.{format} ) > > And if anyone from Twitter is out there listening, the crazy limit you > put on "from:" search queries is why I need an individual status get. > Why do so few records get returned with a "from:" query? Are you folks > worried someone will make a copycat site using "from:"? This limit is > making it really hard to finish my research. I am comparing all the > tweets from 60 users with the mentions of those tweets in the greater > community. I can search the last few days of cached data just fine for > the mentions (searching on @users) but I get almost nothing back when > I search with "from:". The "from:" results in some cases include only > 1 day of data. So I am continually missing out on the original status > message, while I can see everyone's response to the message with no > problem. The from: limit is really painful. Can you help me out? I > would really like to graduate while I am still young. For now I can > manually look up each status I miss, so how do I get the status (in > JSON, I don't want to scrape the author's page, which I guess would be > my fall back approach) > > Thanks! > Jim Skinner > Santa Clara University > > -- > Twitter developer documentation and resources: https://dev.twitter.com/doc > API updates via Twitter: https://twitter.com/twitterapi > Issues/Enhancements Tracker: > https://code.google.com/p/twitter-api/issues/list > Change your membership to this group: > https://groups.google.com/forum/#!forum/twitter-development-talk > > > -- > Twitter developer documentation and resources: https://dev.twitter.com/doc > API updates via Twitter: https://twitter.com/twitterapi > Issues/Enhancements Tracker: > https://code.google.com/p/twitter-api/issues/list > Change your membership to this group: > https://groups.google.com/forum/#!forum/twitter-development-talk > -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk
