Returns a collection of relevant Tweets matching a specified query.
Please note that Twitter’s search service and, by extension, the Search API is not meant to be an exhaustive source of Tweets. Not all Tweets will be indexed or made available via the search interface.
In API v1.1, the response format of the Search API has been improved to return Tweet objects more similar to the objects you’ll find across the REST API and platform. You may need to tolerate some inconsistencies and variance in perspectival values (fields that pertain to the perspective of the authenticating user) and embedded user objects.
To learn how to use Twitter Search effectively, consult our guide to Using the Twitter Search API. See Working with Timelines to learn best practices for navigating results by since_id and max_id.
Parameters | |
q string optional | Specifies the number of tweets to try and retrieve, up to a
maximum of 200. The value of count is best thought of as a limit to the number
of tweets to return because suspended or deleted content is removed after the
count has been applied. We include retweets in the count, even if |
geocode array optional | Returns results with an ID greater than (that is, more recent than) the specified ID. There are limits to the number of Tweets which can be accessed through the API. If the limit of Tweets has occured since the since_id, the since_id will be forced to the oldest ID available. Example: 12345 |
max_id integer optional | Returns results with an ID less than (that is, older than) or equal to the specified ID. Example: 54321 |
trim_user boolean optional | When set to either true, t or 1, each tweet returned in a timeline will include a user object including only the status authors numerical ID. Omit this parameter to receive the complete user object. Example: true |
contributor_details boolean optional | This parameter enhances the contributors element of the status response to include the screen_name of the contributor. By default only the user_id of the contributor is included. Example: true |
include_entities boolean optional | The |
title string | The title Example: The Title |
coordinates array | The coordinates Example: [100.4, 45.1] |
Example[ { "title": "The Title", "coordinates": [ 100.4, 45.1 ] } ] |