Twitter-API-v2-sample-code | Sample code for the Twitter API v2 endpoints | REST library

As you have already loaded the response into dict object of python, you can use key to get the text field as below:

It's hard to troubleshoot what might be going on here. A couple of suggestions.

1. Check out this page.
2. In line 39, remove the .json() from response.json() and run the code again. Once you've done that, you can troubleshoot your code in the interactive command-line very of Python.

To be clear, go to your terminal, enter Python, and then load your functions one by one (Except main()). Then go through the code in main() code one line at a time. After you run json_response = connect_to_endpoint(url, headers) you should still get an error, however, you can then use the objects in the response.request object to see what is going on. For example, after doing the above and then running...

Have you explored the Twitter API documentation for filtered stream yet?

You can learn how to get started with this endpoint group quickly with the quick start guide: https://developer.twitter.com/en/docs/twitter-api/tweets/filtered-stream/introduction

We also have details on how to request additional fields here: https://developer.twitter.com/en/docs/twitter-api/data-dictionary/using-fields-and-expansions

The API Reference for filtered stream describes all of the parameters and fields that you can use with those endpoints: https://developer.twitter.com/en/docs/twitter-api/tweets/filtered-stream/introduction

And finally, we have different pages describing how to pull different types of content, such as Tweet annotations, metrics, and conversation IDs.

Cursoring as documented on that page applies to version 1.1 of the Twitter API, and you are targeting v2. You've also linked to a streaming API sample code example, but you've specified a REST recent search endpoint, which does not support streaming.

You need to use the next_token from the response to paginate in v2.

So you get the first page of results using:

https://api.twitter.com/2/tweets/search/recent?query=snow

And then take the next_token from the response and use it in the next query, for example:

https://api.twitter.com/2/tweets/search/recent?query=snow&next_token=b26v89c19zqg8o3fobd8v73egzbdt3qao235oql

You need to use the Filtered Stream (not the Sampled Stream) in order to target specific values or hashtags. Check the Filtered Stream sample.

The rules values specify what you are listening for - these are sent to a separate endpoint, and are not specified in the header.

In the case of the sample code, this is setup here: