R interface to the Meetup API (v3)
To install the development version from GitHub:
# install.packages("remotes")
remotes::install_github("rladies/meetupr")A released version will be on CRAN soon.
In order to use this package, you can use our built-in
OAuth credentials
(recommended), or if you prefer, you can supply your own by setting the
meetupr.consumer_key and meetupr.consumer_secret variables.
Each time you use the package, you will be prompted to log in to your meetup.com account. The first time you run any of the meetupr functions in your session, R will open a browser window, prompting you to “Log In and Grant Access” (to the meetupr “application”).
Note: As of August 15, 2019, Meetup.com switched from an API key based
authentication system to OAuth 2.0, so we added
support for OAuth. For
backwards compatibility, the functions all still have an api_key
argument which is no longer used and will eventually be
deprecated.
We currently have the following functions:
get_members()get_boards()get_events()get_event_attendees()get_event_comments()get_event_rsvps()find_groups()
Each will output a tibble with information extracted into from the API
as well as a list-col named *_resource with all API output. For
example, the following code will get all upcoming events for the
R-Ladies San Francisco
meetup.
library(meetupr)
urlname <- "rladies-san-francisco"
events <- get_events(urlname, "past")
#> Meetup is moving to OAuth *only* as of 2019-08-15. Set
#> `meetupr.use_oauth = FALSE` in your .Rprofile, to use
#> the legacy `api_key` authorization.
#> Downloading 60 record(s)...
dplyr::arrange(events, desc(created))
#> # A tibble: 60 x 21
#> id name created status time local_date
#> <chr> <chr> <dttm> <chr> <dttm> <date>
#> 1 2730… A co… 2020-09-04 11:04:50 past 2020-09-10 15:30:00 2020-09-10
#> 2 2724… Tang… 2020-08-06 12:24:51 past 2020-08-27 17:30:00 2020-08-27
#> 3 2679… R-La… 2020-01-16 10:08:03 past 2020-01-30 17:00:00 2020-01-30
#> 4 2663… Dece… 2019-11-11 14:10:10 past 2019-12-10 18:00:00 2019-12-10
#> 5 2651… Work… 2019-09-23 12:28:24 past 2019-10-16 18:00:00 2019-10-16
#> 6 2632… Augu… 2019-07-17 10:29:10 past 2019-08-07 18:00:00 2019-08-07
#> 7 2627… R-La… 2019-06-28 15:24:12 past 2019-07-21 11:00:00 2019-07-21
#> 8 2626… Baye… 2019-06-26 20:11:16 past 2019-07-17 18:00:00 2019-07-17
#> 9 2610… Mini… 2019-04-30 17:49:52 past 2019-05-18 13:30:00 2019-05-18
#> 10 2590… NLP … 2019-02-15 14:36:58 past 2019-03-12 18:00:00 2019-03-12
#> # … with 50 more rows, and 15 more variables: local_time <chr>,
#> # waitlist_count <int>, yes_rsvp_count <int>, venue_id <int>,
#> # venue_name <chr>, venue_lat <dbl>, venue_lon <dbl>, venue_address_1 <chr>,
#> # venue_city <chr>, venue_state <chr>, venue_zip <chr>, venue_country <chr>,
#> # description <chr>, link <chr>, resource <list>Next we can look up all R-Ladies groups by “topic id”. You can find
topic ids for associated tags by querying
here.
The topic_id for topic, “R-Ladies”, is 1513883.
groups <- find_groups(topic_id = 1513883)
#> Downloading 138 record(s)...
dplyr::arrange(groups, desc(created))
#> # A tibble: 138 x 21
#> id name urlname created members status organizer lat
#> <int> <chr> <chr> <dttm> <int> <chr> <chr> <dbl>
#> 1 3.38e7 R-La… rladie… 2020-06-12 22:50:37 259 active R-Ladies… -1.29
#> 2 3.34e7 R-La… rladie… 2020-02-22 09:51:34 37 active R-Ladies… 52.4
#> 3 3.34e7 R-La… rladie… 2020-02-22 09:39:39 9 active R-Ladies… 43.3
#> 4 3.32e7 R-La… rladie… 2020-01-12 09:47:12 281 active R-Ladies… 25.7
#> 5 3.32e7 R-La… rladie… 2020-01-12 09:39:04 24 active R-Ladies… 51.8
#> 6 3.31e7 R-La… rladie… 2019-12-15 11:50:22 68 active R-Ladies… 38.9
#> 7 3.31e7 R-La… rladie… 2019-12-15 05:30:12 38 active R-Ladies… 6.93
#> 8 3.31e7 R-La… rladie… 2019-11-30 08:55:10 36 active R-Ladies… 30.0
#> 9 3.31e7 R-La… rladie… 2019-11-30 08:09:20 7 active R-Ladies… 43.0
#> 10 3.30e7 R-La… rladie… 2019-11-23 11:14:43 78 active R-Ladies… 19.0
#> # … with 128 more rows, and 13 more variables: lon <dbl>, city <chr>,
#> # state <chr>, country <chr>, timezone <chr>, join_mode <chr>,
#> # visibility <chr>, who <chr>, organizer_id <int>, organizer_name <chr>,
#> # category_id <int>, category_name <chr>, resource <list>We are looking for new people to join the list of contributors! Please take a look at the open issues, file a new issue, contribute tests, or improve the documentation. We are also looking to expand the set of functions to include more endpoints from the Meetup API. Lastly, we’d also love to hear about any applications of the meetupr package, so we can compile a list of demos!
Please note that the this project is released with a Contributor Code of Conduct. By contributing to this project, you agree to abide by its terms.
React
Typescript
Django
Laravel
Facebook
Microsoft
Google
Alibaba
D3
Tencent