Would it be possible to add access to the guest count to the API?
Even if if was just for the organiser, i.e. the person under whose
account the meetup was created through the API, that would work.
The guest counts can be retrieved through the /2/rsvps methods (in the guests field) and can be modified by POSTing a new RSVP to the /2/rsvp method for the same event_id and member_id, modifying the guests parameter there. You will probably also want to copy the RSVP comments (and survey questions, if you're using them in your group) from the old RSVP to the new one.
Organizers can create or edit other people's RSVPs in their group; normal users can of course only change their own RSVP.
(Note that the POST /2/rsvp method is new, but the version 1 API should work similarly here if you need to keep using it for some reason.)
cheers, mlc
On 02/26/2012 11:53 AM, Phokus wrote:
> Would it be possible to add access to the guest count to the API? > Even if if was just for the organiser, i.e. the person under whose > account the meetup was created through the API, that would work.
-- mike castleman android developer, meetup mailto:m...@meetup.com
On Sunday, February 26, 2012 10:52:21 AM UTC-8, Mike Castleman wrote:
> You will probably also want to copy the RSVP comments > (and survey questions, if you're using them in your group) from the old > RSVP to the new one.
Hmmh. Does this imply I can remove and/or change RSVP comments? That would be nice! Sometimes members leave stupid (or obsolete) information in those comments. The most inane one is "Please let me attend" - long after they make it into the YES RSVP list or "I'll be there at 8:00 pm" even when they have moved themselves to No.
On Sun, Mar 4, 2012 at 5:18 PM, Steven <steventheamus...@gmail.com> wrote:
> On Sunday, February 26, 2012 10:52:21 AM UTC-8, Mike Castleman wrote:
>> You will probably also want to copy the RSVP comments >> (and survey questions, if you're using them in your group) from the old >> RSVP to the new one.
> Hmmh. Does this imply I can remove and/or change RSVP comments?
You can update event survey questions through the 2/rsvp API. See the parameter notes section
On Monday, March 5, 2012 11:49:15 AM UTC-8, Doug Tangren wrote:
> On Sun, Mar 4, 2012 at 5:18 PM, Steven wrote:
>> On Sunday, February 26, 2012 10:52:21 AM UTC-8, Mike Castleman wrote:
>>> You will probably also want to copy the RSVP comments >>> (and survey questions, if you're using them in your group) from the old >>> RSVP to the new one.
>> Hmmh. Does this imply I can remove and/or change RSVP comments?
> You can update event survey questions through the 2/rsvp API. See the > parameter notes section
{"details":"API requests must be key-signed, oauth-signed, or accompanied by a key: http:\/\/www.meetup.com\/meetup_api\/docs\/#authentication","problem":"You are not authorized to make that request"}
I just through some markup in an HTML form... <form name="myform" method="POST" action="http://api.meetup.com/2/rsvps"> <input type="member_id" size="10" value="13025968"> <select name="rsvp"> <option value="waitlist">waitlist</option> <option value="yes" selected>yes</option> <option value="no">no</option> <-- I selected this I am trying to change my own RSVP for which I have 2 guests and a YES status. <option value="maybe">maybe</option> </select> <input type="text" name="event_id" value="53132612"> <input type="hidden" name="key" value="MYKEYISHERE"> <input type="submit" name="mysubmit" value="Submit" />
Doesn't seem to work even when I put the matching guest number, etc.
On Mon, Mar 5, 2012 at 5:58 PM, Steven <steventheamus...@gmail.com> wrote: > On Monday, March 5, 2012 11:49:15 AM UTC-8, Doug Tangren wrote:
>> On Sun, Mar 4, 2012 at 5:18 PM, Steven wrote:
>>> On Sunday, February 26, 2012 10:52:21 AM UTC-8, Mike Castleman wrote:
>>>> You will probably also want to copy the RSVP comments >>>> (and survey questions, if you're using them in your group) from the old >>>> RSVP to the new one.
>>> Hmmh. Does this imply I can remove and/or change RSVP comments?
>> You can update event survey questions through the 2/rsvp API. See the >> parameter notes section
> {"details":"API requests must be key-signed, oauth-signed, or accompanied > by a key: http:\/\/www.meetup.com\/meetup_api\/docs\/#authentication","problem":"You > are not authorized to make that request"}
> I just through some markup in an HTML form... > <form name="myform" method="POST" action="http://api.meetup.com/2/rsvps"> > <input type="member_id" size="10" value="13025968"> > <select name="rsvp"> > <option value="waitlist">waitlist</option> > <option value="yes" selected>yes</option> > <option value="no">no</option> <-- I selected this I am trying to > change my own RSVP for which I have 2 guests and a YES status. > <option value="maybe">maybe</option> > </select> > <input type="text" name="event_id" value="53132612"> > <input type="hidden" name="key" value="MYKEYISHERE"> > <input type="submit" name="mysubmit" value="Submit" />
> Doesn't seem to work even when I put the matching guest number, etc.
> Hints anyone?
You really don't want to expose your api key on the client but rather have it stored on the server where no one can access it.
I think the error you are seeing is that your the url you are posting to is 2/rsvps and not 2/rsvp
On Monday, March 5, 2012 3:54:32 PM UTC-8, Doug Tangren wrote:
> You really don't want to expose your api key on the client but rather have > it stored on the server where no one can access it.
> I think the error you are seeing is that your the url you are posting to > is 2/rsvps and not 2/rsvp
Duh. The extra s was a problem, *thanks Doug.* I did notice one quirk. I didn't specify the guest parameter and I changed a guest who was a +1 to "yes" from "waitlist" and it knocked the guest off.
PS. I am desk checking this, so the key is only in my browser locally. Thanks for the warning, though.
Last question: Is there a way I can bulk change a bunch 'o RSVPs at once? Clearly I can't put MemID1,MemID2 ...
On Tue, Mar 6, 2012 at 12:03 AM, Steven <steventheamus...@gmail.com> wrote:
> On Monday, March 5, 2012 3:54:32 PM UTC-8, Doug Tangren wrote:
>> You really don't want to expose your api key on the client but rather >> have it stored on the server where no one can access it.
>> I think the error you are seeing is that your the url you are posting to >> is 2/rsvps and not 2/rsvp
> Duh. The extra s was a problem, *thanks Doug.* I did notice one quirk. I > didn't specify the guest parameter and I changed a guest who was a +1 to > "yes" from "waitlist" and it knocked the guest off.
> PS. I am desk checking this, so the key is only in my browser locally. > Thanks for the warning, though.
> Last question: Is there a way I can bulk change a bunch 'o RSVPs at once? > Clearly I can't put MemID1,MemID2 ...
Not with one request, no. I probably wouldn't encourage that either because it would confuse users when they visit the site unless they've authorized your app to do so.
On Monday, March 5, 2012 9:06:18 PM UTC-8, Doug Tangren wrote:
> On Tue, Mar 6, 2012 at 12:03 AM, Steven wrote:
>> Last question: Is there a way I can bulk change a bunch 'o RSVPs at once? >> Clearly I can't put MemID1,MemID2 ...
>> Not with one request, no. I probably wouldn't encourage that either > because it would confuse users when they visit the site unless they've > authorized your app to do so.
Only organizers/hosts will be using this app (and only they have the power to change other's RSVPs). I realize there is another wrinkle to this plan based on my testing. The reason we'd want to do it in bulk is we'd like to make it autonomous.
Since the point of the tool is to correct problems with the Yes and Wait list (e.g. manually move people to and from various status), is there a programmatic way to turn off RSVPs (e.g. "Close RSVPs" as the UI calls it?). If not, it means that moving someone from Yes to No or waitlist will trigger the "automatic" or manual behavior of waitlists which is NOT what we want. We'd like the waitlist to lie dormant while we update the list. We also don't want it to "automagically" increase the attendee count during the process. E.g. if I move someone from Wait to Yes, I don't want it to increase the limit by one. It doesn't seem to be doing this now, fortunately.
One last thing I'd like to do is move someone from the waitlist to the end of the waitlist (for an automatic wait list). I'll test to see if changing them to No then back to wait will do the trick. Why would we do this? We want to move people with prior no-shows to the back of the line. I'm not particularly worried if they get two email notifications about this, but it would be just as well if the automatic emails could also be turned off - or customized.
Hmmh, discovered another wrinkle. "{"details":"You must be an organizer to RSVP to the event for someone else.","problem":"You are not authorized to make that request"}"
I used an API key for a person who is a HOST for the event that is being operated upon. The host has "Update RSVP" privileges for the event in the UI, but apparently the API does not allow this operation. Moreover, it would appear the HOST cannot update their *own *RSVP through the API if they supply their member id. (I'm using keys, not Oauth here).
This is a bit disconcerting as implies that the only way I can get my hosts to be able to manage their events via the Tool I'm writing is to have them use an organizer key.
On Tue, Mar 6, 2012 at 4:05 PM, Steven <steventheamus...@gmail.com> wrote: > Hmmh, discovered another wrinkle. > "{"details":"You must be an organizer to RSVP to the event for someone > else.","problem":"You are not authorized to make that request"}"
> I used an API key for a person who is a HOST for the event that is being > operated upon. The host has "Update RSVP" privileges for the event in the > UI, but apparently the API does not allow this operation. Moreover, it > would appear the HOST cannot update their *own *RSVP through the API if > they supply their member id. (I'm using keys, not Oauth here).
> This is a bit disconcerting as implies that the only way I can get my > hosts to be able to manage their events via the Tool I'm writing is to have > them use an organizer key.
> Is there a less insecure alternative?
Hi again Steve,
This wasn't something we supported in the past but have no reason not to in the future. I'll put a ticket in to add support for letting a host of an event edit the rsvp list through the API.
On Tue, Mar 6, 2012 at 4:23 PM, Doug Tangren <d...@meetup.com> wrote:
> On Tue, Mar 6, 2012 at 4:05 PM, Steven <steventheamus...@gmail.com> wrote:
>> Hmmh, discovered another wrinkle. >> "{"details":"You must be an organizer to RSVP to the event for someone >> else.","problem":"You are not authorized to make that request"}"
>> I used an API key for a person who is a HOST for the event that is being >> operated upon. The host has "Update RSVP" privileges for the event in the >> UI, but apparently the API does not allow this operation. Moreover, it >> would appear the HOST cannot update their *own *RSVP through the API if >> they supply their member id. (I'm using keys, not Oauth here).
>> This is a bit disconcerting as implies that the only way I can get my >> hosts to be able to manage their events via the Tool I'm writing is to have >> them use an organizer key.
>> Is there a less insecure alternative?
> Hi again Steve,
> This wasn't something we supported in the past but have no reason not to > in the future. I'll put a ticket in to add support for letting a host of an > event edit the rsvp list through the API.
Event hosts should now be able to modify the rsvp list for the event they are hosting.
On Tuesday, March 13, 2012 2:16:21 PM UTC-7, Doug Tangren wrote:
> I used an API key for a person who is a HOST for the event that is being >>> operated upon. The host has "Update RSVP" privileges for the event in the >>> UI, but apparently the API does not allow this operation. Moreover, it >>> would appear the HOST cannot update their *own *RSVP through the API if >>> they supply their member id. (I'm using keys, not Oauth here).
>>> This is a bit disconcerting as implies that the only way I can get my >>> hosts to be able to manage their events via the Tool I'm writing is to have >>> them use an organizer key.
>>> Is there a less insecure alternative?
>> Hi again Steve,
>> This wasn't something we supported in the past but have no reason not to >> in the future. I'll put a ticket in to add support for letting a host of an >> event edit the rsvp list through the API.
> Event hosts should now be able to modify the rsvp list for the event they > are hosting.
