Thanks Mark and Matt for the help. solved the problem :)
On Mon, May 9, 2011 at 9:02 PM, Matt Harris wrote:
> Hi Abhi,
>
> As Mark mentions, since_id is a Tweet ID not a unix timestamp. Right now
> this is in the region of 67770831463395328.
>
> If you want to Search since a certain date you can
Hi Abhi,
As Mark mentions, since_id is a Tweet ID not a unix timestamp. Right now
this is in the region of 67770831463395328.
If you want to Search since a certain date you can include the parameter
since:-mm-dd in your query parameter. e.g:
http://search.twitter.com/search.atom?lang=en&rpp=
since_id values are tweet ID's, not unix timestamps.
On Mon, May 9, 2011 at 8:47 PM, Abhishek Jain wrote:
> Hi Matt, thanks for the quick response:
>
>
> http://search.twitter.com/search.atom?lang=en&rpp=100&result_type=mixed&q=%22Hell+To+Pay%22+Neal+Hall&since_id=
> *1304633831*
>
> However unix
Hi Matt, thanks for the quick response:
http://search.twitter.com/search.atom?lang=en&rpp=100&result_type=mixed&q=%22Hell+To+Pay%22+Neal+Hall&since_id=
*1304633831*
However unix time 1304633831 stands for May 5th is that too old for the
twitter API?
Cheers,
Abhi
On Mon, May 9, 2011 at 8:42 PM,
Hi Abhi,
The ID you are passing is 1304977102 which is really old. If you are not
sure which since_id to use you should omit it from your query. The response
from the API will then include the oldest since_id available.
Remember the Search API only stores the last 7 days worth of Tweets.
Anything
sample url
:http://search.twitter.com/search.atom?lang=en&rpp=100&result_type=mixed&q=%22Geometry+Essentials+For+Dummies%22+Mark+Ryan&since_id=1304977102
all my twitter search api calls (with since_id in them ) are returning since
date or since_id is too old"
--
Twitter developer documentation