More than 10 results in trends/place.json endpoint

alvelascof · 2015-12-03T08:23:04.990Z

Hello,

I have noticed that trends/place.json operation is returning more than 10 trending topics since 2015-12-02 23:10:00 UTC (no matter what WOEID used).

Does anyone know if this is a change of specifications or a bug?

Thank you.

BuKinoshita · 2015-12-04T13:26:56.892Z

Yea, I’m getting this too.

OscarClar1 · 2015-12-07T16:59:01.163Z

Same problem here with trends. Any suggest?

andrs · 2015-12-10T11:41:17.758Z

Thanks for bringing this to our attention - this is actually intended behavior which you should see reflected in the relevant docs where these changes took place:

GET trends/personalized
GET trends/place

Additionally, we are also now returning a tweet_volume for each trend - this is the volume of tweets per trend for the last 24 hours.

richardhyland · 2015-12-11T09:07:17.568Z

andrs:

GET trends/personalized

Is trends/personalized actually an endpoint as I get an access denied trying to access even the documentation?

andrs · 2015-12-11T09:40:14.021Z

The GET trends/personalized is a private endpoint that requires whitelisting - if you don’t have access to it, don’t worry about it as it will not affect you in any way

andypiper · 2015-12-11T09:54:11.069Z

To clarify, this endpoint is primarily related to the Ads API - thus the whitelisting.

johnbarratt · 2015-12-11T22:22:03.272Z

Thanks for the updates. Regarding the new tweet_volume field, sometimes it isn’t populated (often null). Is that the way it will always be to some extent, or is Twitter working to always have this field populated in these results?

Thanks

andypiper · 2015-12-15T14:10:44.266Z

Hey @johnbarratt - thanks for the follow-up. I don’t have anything to share to clarify that at the moment, we’ll try to get more information on that for you when we can.