Meetup.com API

[allella]

http://www.meetup.com/meetup_api/

[allella]

@rhynodesigns Not sure if this Rails model is of any help, but perhaps there's something to glean.

https://github.com/calagator/calagator/blob/master/app/models/source_parser/meetup.rb

It's from Portland's Calagator, which does both the aggregation and a big arse calendar of everything. This was mentioned in #3

[KCulture]

I also checked out the meetup api.. Seems simple enough to try some test code I might try and use ceylon for it is a lang that I am interested in.

[allella]

Linking this issue over to the comments on another issue about how to find the Meetup.com group_id key values used by Meetup's API.

https://github.com/codeforgreenville/UpstateEvents/issues/15#issuecomment-68424187

[KCulture]

Hey I updated many from meetup . Also I believe that the greer programming group has switched from meetup so I am emailing the organizer

[allella]

Great.

[KCulture]

Do you want me to do anything else .. I am not sure what do for iCal, private e-mails, or rss feeds just let me know

[allella]

@smoking-peanuts Tried to @ you in the iCal thread, but it wouldn't let me. See not on iCal https://github.com/codeforgreenville/UpstateEvents/issues/14#issuecomment-68460199

[allella]

Console for testing the API https://secure.meetup.com/meetup_api/console/?path=/2/groups

[allella]

How to lookup a group's ID via their URL name https://github.com/codeforgreenville/UpstateEvents/issues/15#issuecomment-68424187

[nullvariable]

Here's a nice PHP library for pulling data from the meetup.com api

https://github.com/rdohms/meetup-api-client

[Nunie123]

@allella I've made good progress on the API for meetup. The Meetup API Key for Greer Programming Group is listed on the Open Data website as '7709021031', but this is incorrect and throws an error when I try to use it with the Meetup API. Currently I'm excluding this group from the Meetup API call.

I'm working on this issue here: https://github.com/Nunie123/upstate_tech_cal_service

[allella]

@Nunie123 if you message me your email I'll set you up with access to change the underlying data. Or, did I already set up an account?

[Nunie123]

@allela I have this working.

The API is running and available at: http://nunes.online/api/gtc

The code for the application is here: https://github.com/Nunie123/upstate_tech_cal_service

Only Meetup.com and EventBrite.com are supported. Other sources, such as facebook, Nvite, Open Collective, had issues that prevented API calls to them to be fully automated. We can discuss further about possible ways to include these sites.

The data is update every 5 minutes.

The endpoint does not support filtering currently. That wouldn't be too hard to implement, but I'd rather talk with someone who intends to use it instead of guessing use cases.

It is hosted on AWS and I'm on my free tier, so currently no cost to host. If we want/need to change host, it's running on a generic ubuntu box, so shouldn't be hard to move.

I'd welcome any feedback people have.

[allella]

Rock on.

I'll try to poke around a bit during the holiday break.

I should be around for the 28th meeting and we can chat and dig in.

[allella]

@Nunie123

I took a look at the data and the first notable item is the Eventbrite data looks to be pulling in events from 10 years earlier.

I'd imagine more of the use cases will on upcoming or recent events so perhaps a filter for past vs future/current would be a useful first filter and keep the payload a lot smaller for the future/recent use cases. Thoughts on that situation?

[Nunie123]

@allella

I agree with you that past events data doesn't have a lot of value. Meetup doesn't even provide past events, so you can only look retrospectively at EventBrite events.

The question is whether to simply get rid of it, make a separate endpoint for future events only, or accept post requests indicating future events only. Right now I'm thinking Id just make a separate endpoint.

[Nunie123]

I have updated the endpoint to go over https.

I've also added date filter options to the endpoint. By default it now provides only future events. A start_date and end_date can be specified in the URL to get specific date ranges. I've updated the readme with more detail on how to use it.

I've created a front-end that runs off this data, which can be viewed here: https://nunie123.github.io/gtc/. The repo is here: https://github.com/Nunie123/gtc. @tomatohorse, from the last meeting, is helping me with design for the front-end.

At the last meeting I was sent an invite to contribute to the codeforgreenville github, but I do not have permission to create new repositories. We had talked about migrating my repos to codeforgreenville, but I'm unsure of the best strategy for doing so. Does it makes sense to just fork them, or do we want some other setup?

[allella]

Good work.

@Nunie123 You should now be able to create a new repository under the CFG Github so you're welcome to move things over as you see fit.

[Nunie123]

@allela The api has been updated to include flag filter parameters, in addition to date parameters (e.g. http://nunes.online/api/gtc?tags=1). Currently it returns an empty array because the only group that has tags, UpstatePHP, does not host events on meetup.com or eventbrite.com.

What are your thoughts on moving further discussion to the repo: https://github.com/codeforgreenville/upstate_tech_cal_service? I currently don't have permissions to open up an issue in the repo.

[allella]

@Nunie123 I've enabled Issues on the upstate_tech_cal_service repo. Feel free to create any open issues there and we can close the issues here and link them to each other for future reference.

[allella]

Closing this issue.

For history, see above. For future conversation see the meetup.com bot and Ed's new upstate_tech_cal_service repo.

[allella]

Wayback Machine has copies of the old v2 REST API docs, which were removed and redirected to the GraphQL docs awhile back.

v2 REST API - GET /events v2 REST API - GET /groups