That's not the intended behavior of the API. Will investigate.

On Mon, Mar 9, 2009 at 15:22, Chad Etzel <[email protected]> wrote:
>
> Wait, I thought that this issue (now fixed) addressed the count part:
> http://code.google.com/p/twitter-api/issues/detail?id=235
>
> I can get more than 20 replies per request now.
>
> Actually, just testing this now shows I can get upwards of 1000
> replies per request... er, is this right?
>
> -Chad
>
> On Mon, Mar 9, 2009 at 6:14 PM, Alex Payne <[email protected]> wrote:
>>
>> Yes, this method should be working, and it should support the since_id
>> parameter. The page is 1 by default. You can only request a count of
>> less than 20, not more than 20.
>>
>> On Mon, Mar 9, 2009 at 13:56, Jeff Bishop <[email protected]> wrote:
>>> I am trying to pull a list of replies from Twitter using:
>>>
>>> http://twitter.com/statuses/replies.xml
>>>
>>> I have tried sending in a since_id parameter and I get a bad error back from
>>> twitter that the page doesn't exist.  Should this be working?
>>>
>>> In addition, the page parameter if  not specified, is it assumed to be 1?
>>>
>>> Also, can the count parameter be allowed here to get  more then the last 20
>>> replies if requested?  It doesn't work either and isn't in the list in the
>>> documentation.
>>>
>>
>>
>>
>> --
>> Alex Payne - API Lead, Twitter, Inc.
>> http://twitter.com/al3x
>>
>



-- 
Alex Payne - API Lead, Twitter, Inc.
http://twitter.com/al3x

Reply via email to