RSVP Yes to a Full Event using API

[Jay Janarthanan]

If I want to make a person on waitlist to Yes on a an event that is full, this can be done using the web site. But looks like the API will not allow me to do it

https://api.meetup.com/2/rsvp , even if rsvp=yes is passed. I still get waitlist as the status

Thanks

Jay

[Doug Tangren]

On Sun, Aug 3, 2014 at 8:42 PM, Jay Janarthanan <j...@jayonsoftware.com> wrote:

If I want to make a person on waitlist to Yes on a an event that is full, this can be done using the web site. But looks like the API will not allow me to do it

https://api.meetup.com/2/rsvp , even if rsvp=yes is passed. I still get waitlist as the status

Hi Jay, 

If a given Meetup event had a limited capacity and the organizer has opted enable a waitlist, when you RSVP yes you're RSVP if automatically transformed into a waitlist response. A waitlist response is like a pending version of yes until a spot is open and claimed. You can programmatically tell of an event supports waitlisting by sending fields=rsvp_rules in /2/events -- http://www.meetup.com/meetup_api/docs/2/events/#response

 

Thanks

Jay

--
--
You received this message because you are subscribed to the Google
Groups "Meetup API" group.
To unsubscribe from this group, send email to
meetup-api+...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/meetup-api?hl=en?hl=en

---
You received this message because you are subscribed to the Google Groups "Meetup API" group.
To unsubscribe from this group and stop receiving emails from it, send an email to meetup-api+...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[salt...@gmail.com]

Hi,

I noticed recently that attempts to change an RSVP via the API are not working. The call seems to complete without errors but if I immediately get the RSVP the response hasn’t been changed. In my case I am trying to change an RSVP from ‘yes’ to ‘waitlist’. I believe this code used to work fine.

The repeating event I’m working with to test this is ‘dzgbgkyslbkb’ via the group organizer account and I am able to change the RSVP fine using the Web site.

My PHP code:

$newResponse = 'waitlist';

$obj = new MeetupRsvps($connection);
$params = array(
       'event_id' => $eventId,
       'member_id' => $memberId,
       'rsvp' => $newResponse);
if (!empty($comments))
       $params['comments'] = $comments;
$res = $obj->setRsvp($params);

Sincerely,

Dominique

[salt...@gmail.com]

Hi,

I have not received a response to my message. Is this problem being investigated?

Dominique

[Doug Tangren]

On Wed, Aug 13, 2014 at 1:28 AM, <salt...@gmail.com> wrote:

Hi,

I have not received a response to my message. Is this problem being investigated?

We haven't heard any other reports of this, I will have a look today.

 

--

[Chris Lewis]

Hello Dominique,

Out of curiosity, are you using this library: https://github.com/blobaugh/Meetup-API-client-for-PHP ?

Assuming you are I'm curious where the setRsvp method is coming from, as I don't see it here: https://github.com/blobaugh/Meetup-API-client-for-PHP/blob/master/MeetupRsvps.class.php

--

[salt...@gmail.com]

I don’t recall where I obtained this library but I have been adding to it over the years so it’s possible I added the setRsvp method. Here is the relevant code from the library. And as I said this feature was working fine in the past.

define('MEETUP_ENDPOINT_RSVP', '/2/rsvp');

    public function setRsvp( $Parameters = array() ) {
        $url = $this->buildUrl( MEETUP_ENDPOINT_RSVP, array() );
      //  echo $url;
        $response =  $this->post( $url, $Parameters )->getResponse();
        return $response;
    }

[Chris Lewis]

Ok, I'd encourage you to test the same operation through curl to demonstrate that it is working as expected. We discourage the use of the API key in actual clients but it is a convenient way to run calls via curl. I just ran several calls like this:

curl -d 'event_id=200710682&rsvp=yes' "https://api.meetup.com/2/rsvp?key=$MUAPI_KEY"

Alternating the 'rsvp' value between 'yes' and 'no', where MUAPI_KEY is my key, and I get the expected result in the JSON response. Immediately issuing a GET to the rsvp by id also results in an agreeable payload. Try it through curl and confirm it's working as expected. Let me know what you find!

[Dominique L]

Hi Chris,

As i mentioned in my post i am attempting to change From a 'yes' to a 'waitlist', not a 'no' as you attempted. You'll have to try with an event that has some people already wsitlisted as was the case in the reported issue.

Dominique

---

From: Chris Lewis
Sent: ‎2014-‎08-‎13 8:22 AM
To: meetu...@googlegroups.com
Subject: Re: [meetup-api] Problems changing RSVP

[Chris Lewis]

Hi Dominique,

The reason I suggested curl was to rule out differences in behavior (and surface potential bugs) between curl and the library. I (mis)understood the general concern to be an inability to change an RSVP via the API, as opposed to changing the state specifically from 'yes' to 'waitlist'.

'waitlist' is actually not a status you can set, via the site or the API. The reason is simple: wait lists accumulate 'yes' responses to events that are currently over capacity. The API docs do state that 'waitlist' is a valid input, and we should probably change that. Attempts to set RSVPs to 'waitlist' are treated as 'yeses', and so when you do this in the context of an event that is not yet at capacity, the result is a 'yes'. Therefore the response you are seeing should indicate that the event in question is not yet at capacity. Otherwise, and if the organizer has enabled a wait list for the event in question, the result will be 'waitlist'.

Let me know if that helps.

[salt...@gmail.com]

Hi Chris,

Thank you for the clarification. I tested this further and it does seem to behave as you suggest. This must be a change in behavior because this feature used to work fine some time ago. The problem with the current behavior is that it makes it impossible to manage the wait list. If I have member A who is “yes” and member B who is “waitlist” and I want to swap them so A is on the wait list I can’t do it. Or is there a way? In the past I would simply set A to “waitlist” and then set B to “yes” in that order but this no longer works as A is automatically changed back to “yes” before I can change B.

Dominique

[salt...@gmail.com]

Hi Chris,

Thinking about his more, I believe the site used to support a couple of different types of waitlists (auto waitlist was one I think) and I believe this feature was simplified and I’m guessing that’s when this behavior changed.

Any suggestions on how to perform wait list management using the API given this new behavior?

Dominique

meetup-api+unsubscribe@googlegro