Standard Twitter Search Api!
Search Twitter is an important feature that displays Twitter conversations about a specific topic or event. While this functionality exists in Twitter, these endpoints allow for more flexibility and power in filtering and ingesting tweets, so you can more easily find relevant data for research.
Build near real-time listening applications program; or generally explore, analyze, and/or act upon Tweets related to topics of interest.
We provide two endpoints for you to search Twitter: recent search and full archive search. These two REST endpoints share a common design and functionality, including their use of a single search query to filter tweets around a particular topic.
These search queries are created using a set of operators that match Twitter and user attributes such as message keywords, hash tags, and URLs. Operators can be combined into queries with Boolean logic and parentheses to help refine query matching behavior.
Both the recent search and full archive search endpoints provide edited tweet metadata. All objects for Tweets created since September 29, 2022 include Tweet edit metadata, even if the Tweet has never been edited.
Every time a Tweet is edited, a new Tweet ID is created. A Twitter edit history is recorded by a sequence of Tweet IDs, starting with the original ID.
These endpoints will always return the most recent edit along with any edit history. Any Tweets collected after the 30-minute editing window will represent their final version. To learn more about editing Tweet metadata, check out the Editing Tweet Basics page.
Once you’ve set up your query and started receiving tweets, these endpoints support navigating the results by time and tweet ID range. This is designed to support two common use cases.
Fetch History:
The request is for a certain period of interest, regardless of the real-time nature of the data. Make a single request and pass all hits using pagination as needed. This is the default mode for searching tweets
Polling or Listening: The request is made in “Are there any new tweets since my last request?” Model. Requests are continuous, and there is often a use case focused on “listening” for tweets of interest in near real-time.
Many operators and query restrictions are exclusive to Academic and Enterprise access, meaning you must use keys and tokens from the application in projects with Academic or Enterprise access to use other features . You can learn more about Twitter in the Endpoints section below.
Both recent searches and tweets returned by the full archive search endpoint contribute to the monthly tweet limit.
Recent searches
The recent search endpoint allows you to programmatically access filtered public tweets from the last week, and is available to all developers who have a developer account and use keys and tokens for applications in the project.
You can authenticate your request using OAuth 1.0a user context, OAuth 2.0 application-only, or OAuth 2.0 authorization code with PKCE.
However, if you want to receive private metrics or a breakdown of organic and promoted metrics in your Tweet results, you will have to use an OAuth 1.0a user context or an OAuth 2.0 authorization code with PKCE and pass the associated user access token with the post users for a given content.
This endpoint can deliver up to 100 tweets per request in reverse chronological order and provides a pagination token to page through a large number of matching tweets.
When using a project with Essential or Elevated access, you can use the basic set of operators and make queries of up to 512 characters. You can access other operators when working with projects with Academic Research Access or Enterprise Access. Items with Academic Research access can query up to 1024 characters, and items with Enterprise access can query up to 4096 characters.
Learn more about access levels.
Full file search
Academic Research Access Only
The v2 full archive search endpoint is only available for projects with academic research access or enterprise access. This endpoint allows you to programmatically access public tweets in the full archive going back to the first tweet in March 2006 based on a search query.
You can authenticate your requests to this endpoint using OAuth 2.0 App-Only, and the application access token must be from an application in a project with academic research access.
Since you cannot use this endpoint to make requests on behalf of another user (OAuth 1.0a user context or OAuth 2.0 authorization code with PKCE), you will not be able to pull private metrics.
This endpoint can serve up to 500 tweets per request in reverse chronological order, and provides a pagination token to page through a large number of matching tweets.
Note:
If comments are requested via the Twitter . Fields parameter, the max-results parameter is currently limited to a maximum value of 100. This may change in the future, but be aware of this limitation.
Since this endpoint is only available to those who have been granted academic research access, you have access to the full set of search operators and can make queries of up to 1024 characters.