The api documentation (http://dev.twitter.com/doc/get/trends/ location/:woeid) lists the url format as http://api.twitter.com/version/trends/location/:woeid.format and shows as an example the following url: http://api.twitter.com/1/trends/location/1.xml This example url in the documentation also throws the error I mentioned.
The urls you provided did work, but I think in this instance the documentation needs to be updated to reflect the correct url format. Let me know if I'm wrong reading the documentation incorrectly. Thanks, Heidi On Jul 6, 1:04 am, Raffi Krikorian <ra...@twitter.com> wrote: > 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 <heidi.hys...@gmail.com> 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 Teamhttp://twitter.com/raffi