We at Meetup HQ realize that sometimes a yes RSVP doesn't guarantee member will actually be present at any given event. In the past we've tried to help with this by providing attendance taking tools.
You may have noticed that attendance taking interfaces look a little different on Meetup.com on mobile devices. We've simplified some things to make attendance taking more straight forward.
We realize that in large events rapidly taking attendance on a member per member basics will likely lead to a rate limiting situation. Our attendance taking API (
http://www.meetup.com/meetup_api/docs/:urlname/events/:id/attendance/#edit ) now accepts a comma delimited list of member ids so you can make the most of one request. The headcount and guests parameter will likely be deprecated soon.
We also realize that viewing attendance listings was non intuitive. The attendance listing API (
http://www.meetup.com/meetup_api/docs/:urlname/events/:id/attendance/#list ) and the tool you'll find on the desktop version of
meetup.com is designed in the reverse way you'd actually take attendance at the event. Rather then marking members attended, all RSVP'd members are implicitly marked attended and you note only the members that were absent or a no show.
We've now merged in the the notion of attendance with our RSVP listing API (
http://www.meetup.com/meetup_api/docs/2/rsvps/ ). Members that are authorized to take attendance in a given group may request attendance_status using the fields parameter. This will enable you to more easily build attendance taking UI's that are a little more intuitive. You start off with an RSVP list and collect member ids to then mark as attended.
The attendance listing API was based on the older attendance taking tool on
meetup.com. This API will likely be deprecated in the future.
We think these simplifications will enable you to build you're own attendance taking tools more easily.
Let us know what you think.
Doug Tangren
Meetup Platform API Engineer