Hi Matt,

thanks for clearing up my questions!

--
Kind Regards,
Rajinder Yadav

On 10-11-29 05:09 PM, Matt Harris wrote:
Hi Rajinder,

We would really like to offer access to the historical timeline but our
infrastructure doesn't allow access to anymore than 3200 right now. The
Tweets are safe and have not been deleted or lost, they are just not
available. We also don't have a timeline for access to historical tweets
right now.

In answer to your second question, when there are no more statuses
available we'll return an HTTP 200 with an empty timeline. For example:

JSON:
[]

XML:
<?xml version="1.0" encoding="UTF-8"?>
<statuses type="array">
</statuses>

Best,
@themattharris
Developer Advocate, Twitter
http://twitter.com/themattharris


On Mon, Nov 29, 2010 at 10:42 AM, Rajinder Yadav <devguy.ca
<http://devguy.ca>@gmail.com <http://gmail.com>> wrote:

    On Mon, Nov 29, 2010 at 12:27 PM, Matt Harris
    <thematthar...@twitter.com <mailto:thematthar...@twitter.com>> wrote:
     > Hi Rajinder.
     > The user_timeline returns upto 200 statuses per page starting
    with the most
     > recent. To retrieve a complete page of 200 you will want to make
    a request
     > similar to:
     >
     >
    
http://api.twitter.com/1/statuses/user_timeline.json?count=200\&include_rts=1
    
<http://api.twitter.com/1/statuses/user_timeline.json?count=200\&include_rts=1>
     > This request will return upto the most recent 200 statuses. To
    retrieve the
     > next 200 you would make this request:
     >
     >
    
http://api.twitter.com/1/statuses/user_timeline.json?count=200\&include_rts=1\&page=2
    
<http://api.twitter.com/1/statuses/user_timeline.json?count=200\&include_rts=1\&page=2>
     > When requesting this many statuses at once you may get a 503
    error response
     > from us. If this happens wait a few seconds and try the request
    again.
     > Hope that helps,
     > @themattharris
     > Developer Advocate, Twitter
     > http://twitter.com/themattharris

    Hi Matt,

    thanks, that is a better solution than what I have been using.
    Questions, am I limited up to only 3200 statuses? is it possible to go
    beyond this limit and get the entire statues for a user?

    When there are no more status request (empty set), what http error
    code can I expect. Likewise if 3200 status is a hard limit what http
    error will I get when this limit is hit?

    Finally if I have exceeded my rate limit what is the http code returned?

    Kind Regards,
    Rajinder Yadav


--
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