I believe the since parameter can only be used to go back 24 hours. From the docs:
> • since. Optional. Narrows the resulting list of direct messages > to just those sent after the specified HTTP-formatted date, up to 24 > hours old. The same behavior is available by setting the If- > Modified-Since parameter in your HTTP request. Ex: > http://twitter.com/direct_messages.atom?since=Tue%2C+27+Mar+2007+22%3A55%3A48+GMT --Eric On Jan 31, 2009, at 6:52 PM, Dimebrain wrote: > > output of unit test (calling since with date prior twitter launch, > fails with closer dates as well) > > without since: http://twitter.com/direct_messages.json > with since: > http://twitter.com/direct_messages.json?since=Fri2c+27+Feb+2004+23%3a50%3a41+GMT > > 20 direct messages found without 'since' > 1 direct messages found with 'since' > -------------------- > > On Jan 31, 4:27 pm, Alex Payne <a...@twitter.com> wrote: >> Sounds like we don't have direct messages for you since the date >> you're specifying :) >> >> On Sat, Jan 31, 2009 at 00:58, Dimebrain <daniel.cre...@gmail.com> >> wrote: >> >>> I'm not able to make a call to get direct messages sent or >>> received by >>> the authenticating user if I add the "since" parameter, passing the >>> correctly formatted / url-encoded date. All I get back is "nil". >> >>> Even with the demo API call in the REST documentation, i.e.: >>> http://twitter.com/direct_messages/sent.xml?since=Tue%2C+27+Mar+2007+ >>> ... >> >>> I am getting a nil response. If I leave off the since parameter, I >>> get >>> all direct messages sent in the query above, including those later >>> than the example date. >> >> -- >> Alex Payne - API Lead, Twitter, Inc.http://twitter.com/al3x
