#1

Hello, I need a tweepy code that makes use of a 1% sample stream to fetch tweets. I’m talking about the Volume streams. I am not able to understand it that’s why I was asking.

#2

Do the docs help? Streaming — tweepy 4.12.0 documentation

1 Like
#3

Possibly. Is this an alternate source of docs for the broken or missing v2 volume API?

https://developer.twitter.com/en/docs/twitter-api/tweets/volume-streams/api-reference

#4

Seeking clarification. Obviously tweepy is a Python based thingpy, correct (pun intended)? Along which lines, speaking in terms of the pure REST, or at least how to render parameters… obvious ones such as bool or int are straightforward enough I think. But what about the following:

  • return_type (type[dict | requests.Response | Response])
  • proxy (str | None), what is ‘None’ exactly? or just that, i.e. “proxy=None”?
  • verify (bool | str), the bool use case seems straightforward, but examples of the str use case?

Then approaching the actual volume sample, presumably that is:

  • sample(*, backfill_minutes=None, expansions=None, media_fields=None, place_fields=None, poll_fields=None, tweet_fields=None, user_fields=None, threaded=False )

In particular, i.e. tweet_fields (list[str] | str) – tweet_fields, assume that has to do with tweet.fields docs in the actual Twitter API docs. Confidence level there is 85%.

I think I could probably fiddle with the response to figure out what’s what, but just curious about the request and REST inputs.

#5

Oh, seems like that docs link broke. This one works: Volume streams introduction | Docs | Twitter Developer Platform

The actual endpoint parameters are in here GET /2/tweets/sample/stream | Docs | Twitter Developer Platform

All the ones from tweepy are library and python specific, and sometimes refer to other things, not the endpoint itself - like proxy is for your connection, nothing to do with the API.

#6

Appreciate the clarification, yes, I was piecing those nuances together, actually. Thanks for responding.

1 Like
#7

Which to be clear, I did not randomly drop that broken link. That is from the page, “Visit the API reference page for this endpoint”:

Y’al should correct that in your page sources.

1 Like