R client for collecting data via Twitter's REST and stream API's.
To get the current released version from CRAN:
To get the current development version from github:
Communicating with Twitter's APIs can, at times, be inconsistent. With that said, if you encounter an obvious bug for which there is not already an active issue, please create a new issue with all code used (preferably a reproducible example) on Github. For questions or other discussion, please use rtweet's Google group.
Quick authorization method: To make your life easier, follow the recommended steps in obtaining and using access tokens. However, for a quick start (note: much slower in long term), you can also follow the instructions below or via the rtweet documentation website.
First, you'll need to create a Twitter app. For the callback field, make sure to enter:
Once you've created an app, record your consumer (api) and secret keys. Screeshots can be found here.
Generate a token by using the
## name assigned to created app appname <- "rtweet_token" ## api key (example below is not a real key) key <- "XYznzPFOFZR2a39FwWKN1Jp41" ## api secret (example below is not a real key) secret <- "CtkGEWmSevZqJuKl6HHrBxbCybxI1xGLqrD5ynPd9jG0SoHZbD" twitter_token <- create_token( app = appname, consumer_key = key, consumer_secret = secret)
twitter_tokenis part of your global environment, rtweet functions should find it. However, using this method, the token will not automatically load in future sessions (you'll need to create a token every time you start a new session).
Although not necessary, functions also accept tokens via the
tokenargument. For example:
rt <- search_tweets("data science", n = 1000, token = twitter_token)
- Recommended authorization method: Obtaining and using access tokens (vignette showing how to sustainably setup authorization to use Twitter's APIs).
More technical description: An implementation of calls designed to extract and organize Twitter data via Twitter's REST and stream API's. Functions formulate GET and POST requests and convert response objects to more user friendly structures, e.g., data frames or lists. Specific consideration is given to functions designed to return tweets data from searches, streams, and timelines and user ids from friends and followers lists.