![]() The query can have operators that modify its behavior. the available operators are: OperatorĬontaining both “watching” and “now”. This is the default operator.Ĭontaining the exact phrase “happy hour”.Ĭontaining either “love” or “hate” (or both). ![]() Sent from a Twitter account in the NASA list astronauts-in-space-nowĪ Tweet authored in reply to Twitter account Twitter account “NASA”.Ĭontaining “politics” with Tweets marked as potentially sensitive removed.Ĭontaining “puppy” and an image or video.Ĭontaining “puppy”, filtering out retweetsĬontaining “puppy” and an uploaded video, Amplify video, Periscope, or Vine.Ĭontaining “puppy” and a Periscope video URL.Ĭontaining “puppy” and links identified as photos, including third parties such as Instagram.Ĭontaining “puppy” and a link representing one or more photos.Ĭontaining “hilarious” and linking to URL.Ĭontaining “puppy” and a URL with the word “amazon” anywhere within it.Ĭontaining “superhero” and sent since date “” (year-month-day).Ĭontaining “puppy” and sent before the date “”.Ĭontaining “movie”, but not “scary”, and with a positive attitude.Ĭontaining “flight” and with a negative attitude.Ĭontaining “traffic” and asking a question. Please, make sure to URL encode these queries before making the request. The table below shows some example mappings from search queries to URL encoded queries: Search query There are several online tools to help you to do that, or you can search at /search and copy the encoded URL from the browser’s address bar. Note that the space character can be represented by “%20” or “+” sign. Geolocalization: the search operator “near” isn’t available in the API, but there is a more precise way to restrict your query by a given location using the geocode parameter specified with the template “latitude,longitude,radius”, for example, “37.781157,-122.398720,1mi”.Result Type: just like /search results, the result_type parameter selects whether the result set will be represented by recent or popular Tweets, or even a mix of both.The GET search/tweets documentation has detailed information about the usage of the parameters, this section will only give a brief description of their capabilities: There is a set of additional parameters that allows a better control of the search results. Iterating in a result set: parameters such count, until, since_id, max_id control iteration through search results, since it could be a large set of Tweets.Language: the lang parameter restricts Tweets to the given language.When conducting geo searches, the search API will first attempt to find Tweets which have lat/long within the queried geocode, and in case of not having success, it will attempt to find Tweets created by users whose profile location can be reverse geocoded into a lat/long within the queried geocode, meaning that is possible to receive Tweets which do not include lat/long information.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |