Why does the /trends/place.json return 404 sometimes for valid WOEIDs?


#1

I’m trying to retrieve trending hashtags via the /trends/place.json API. I’m using flickr’s flickr.places.findByLatLon() api to retrieve WOEID for a (lat,lon) pair. Twitter’s /trends/place.json API returns 404 for most of the times(may be 8 out of 10 times). Why does this happen?

Eg:
works for woeid = 2508428,
doesn’t work for woeid = 55895261,12587688,2488142,2487384,2385382


#2

Okay. Turns out /trends/place.json supports only very few WOEIDs given by /trends/available.json API.

So, my option was to use /trends/closest API by passing the lat and lon values directly.