hey heidi. can you provide more information? i just tried the following few things:
http://api.twitter.com/1/trends/2487956.xml (trends in SF) http://api.twitter.com/1/trends/2487956/current.xml (same as above) http://api.twitter.com/1/trends/2487956/hourly.xml (hourly version 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 <[email protected]> wrote: > 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 > timescale. I try and send in the "timescale=current" as a parameter, > however it still gives me the same error. > I've tried using different woeid's and they all result in the same > error. > Using the twitter provided console also yields the same error (http:// > dev.twitter.com/console). > > Any insight is appreciated. > > Thanks, > Heidi > -- Raffi Krikorian Twitter Platform Team http://twitter.com/raffi
