[twitter-dev] Re: Invalid timescale error on location trends

2010-07-06 Thread Heidi Hysell
ersion of > trends > from SF)http://api.twitter.com/1/trends/2487956/daily.xml(the day's trends > from SF) > > and those worked.  what's the exact call you're trying? > > > > On Mon, Jul 5, 2010 at 2:35 PM, Heidi Hysell wrote: > > I'm trying to u

[twitter-dev] Invalid timescale error on location trends

2010-07-05 Thread Heidi Hysell
I'm trying to use the trends/location/woeid functionality (http:// dev.twitter.com/doc/get/trends/location/:woeid) and keep on getting the following error: code: 31 message: "Invalid timescale: must be 'current', 'hourly', or 'daily'" The documentation doesn't specify anything about sending in a t