RSVP Create/Update
Creates or updates an existing RSVP
Request Parameters
At least one of the required parameter(s) must be supplied with the request.
The RSVP is recorded for the currently authenticated member account, unless a member_id is supplied, in which case the authenticated member must have permissions to edit the event or a host.
Member's RSVP'ing as themselves may supply answers to a Meetup event's survey questions by supplying answers as request parameters corresponding to question ids in the format answer_{question_id}. To discover available Meetup event survey questions, supply the Events 2 method with the 'fields' parameter set to 'survey_questions'.
Repeated attempts to RSVP to the same event given the same member credentials will result in an update to previous RSVP. The state of the event may or may not allow for this update to occur depending on the organizer-defined constraints and pre-requisites for the event.
Note: waitlist responses may be coerced into yes responses when there is space available and yes responses may be coerced into waitlist response when space is not.
If the event requires payment you are required to send an "agree_to_refund" parameter set to the true or false. This represents the authorized members agreement to understanding the event's refund policy.
- agree_to_refund
- For events with fees, the authorized member must agree to the event's refund policy. This must be set to either true or false
- answer_{qid}
- Answers to event survey questions. Answers may not be longer than 250 characters. Organizers and hosts my not edit or create answers on behalf of members
- comments
- A comment to post along with the RSVP
- event_id
- The event that you are RSVP'ing to
- guests
- Number of guests also coming to the event.
- member_id
- Organizers and event hosts may RSVP on behalf of a member by specifying an ID here. As when editing RSVPs on the site, organizers may enter a "yes" for a member even if the event requires payment.
- opt_to_pay
- For events with fees, the authorized member may opt to pay as part of the RSVP request. This may be set to true or false
- rsvp
- The RSVP setting - value must be either "yes", "no" or "waitlist"
Response
If successful, this method returns a 201 Created response with a Location header containing the RSVP Get method for this event. 401 Unauthorized is returned if the currently authenticated member can not create Meetups in the specified group.
In cases where a member successfully RSVP's yes to one of these events, the response will be returned as an HTTP 202 Accepted status, representing that the payment processing has not yet been completed. A payment_redirect property will be appended to the response containing the value of the step you should take to submit the payment online for the event.
If a validation of Event and RSVP state occurs you may wish to inspect the response body for one of these the following error "codes".
'dues_required': You must pay the group's member dues on the full site before you can RSVP for this event
'event_past': This event has already passed
'invalid_event': Invalid event
'invalid_guest_num': Invalid number or guests
'invalid_response': Invalid RSVP response
'payment_required': Payment required to RSVP
'refund_agreement': Member must agree to refund policy
'rsvp_closed': Sorry. RSVPs are now closed so you can't add any more guests.
'rsvp_error': Error RSVPing to event
'rsvper_not_authorized': You need to be an organizer or an event host to RSVP this member
'too_few_spots': There are not enough spots for your rsvp
'too_many_guests': You have specified too many guests
- answers
-
List of answers to event survey questions asked when the member RSVP'd in the order asked, only available to organizers and assistant organizers. By default, this field returns a list of strings answers. You can request more structured answer info including the time the answer was updated, by setting fields=answer_info in the request
- answer
-
The members provided answer to the question
- question
-
The text of the question asked of the member
- question_id
-
The unique id of the question answered
- updated
-
The time the answer was last modified in milliseconds since the epoch
- comments
-
The message that the member provided when RSVP was made
- created
-
Creation time of the RSVP, in milliseconds since the epoch.
- event
-
The event associated with the RSVP
- event_url
-
URL of the event's page on meetup.com
- id
-
String ID of the event
- name
-
Name of the event
- time
-
UTC start time of the event, in milliseconds since the epoch
- group
-
Group hosting the event
- created
-
Date and time that the group was founded, in milliseconds since the epoch
- group_lat
-
Approximate group latitude
- group_lon
-
Approximate group longitude
- id
-
Group id
- join_mode
-
"open", "approval", or "closed"
- name
-
Group name
- urlname
-
Group URL name
- who
-
What the group calls its members
- guests
-
Number of guests the RSVP'd member will be bringing
- host
-
Optional field, `true` if RSVP is for an event host
- member
-
Member who RSVP'd
- bio
-
Optional field returned when appending "member_bio" to the "fields" parameter. Contains the member's group "introduction"
- member_city
-
Optional field
- member_country
-
Optional field
- member_id
-
Member's ID
- member_state
-
Optional field
- name
-
Name of the member
- other_services
-
Third-party services associated with the member account
- [service-name]
- This element is flickr, tumblr, twitter, or linkedin
- member_photo
-
Rsvping Member's photo
- highres_link
-
URL for the photo at its maximum size
- photo_id
-
Photo ID
- photo_link
-
URL for a standard size of the photo
- thumb_link
-
URL for a thumbnail of the photo
- mtime
-
Last modified time of the RSVP, in milliseconds since the epoch.
- pay_status
-
The RSVPer's payment status if the event has an associated fee. Returned only for organizers when 'pay_status' is requested with the fields parameter. This may be one of 'none', 'paid', 'partially_paid', 'payment_pending', 'echeck_pending', 'refund_pending', 'partially_refunded', 'refunded'.
- payment_redirect
-
If the event RSVP'd to requires online payment and a yes response was accepted, this field will contain a payment URL you should redirect the authenticated member to in order to complete the online payment
- response
-
"yes", "no", "waitlist" or "yes_pending_payment" which is the response returned after RSVPing "yes" to an event that requires payment.
- rsvp_id
-
The RSVP id
- tallies
-
The current set of counts for RSVPs
- maybe
-
Number of maybe rsvps
- no
-
Number of no rsvps
- yes
-
Number of yes rsvps
- venue
-
Venue, if selected and not hidden
- address_1
-
Line 1 of venue address
- address_2
-
Line 2 of venue address
- address_3
-
Line 3 of venue address
- city, state, country
-
City, Country and if in US state of venue
- id
-
Venue id
- lat, lon
-
Geographic coordinates of venue
- name
-
Venue name
- phone
-
Phone number of venue
- repinned
-
true if the editor of the event altered the original venues pin location, false otherwise
- zip
-
ZIP code if, venue is in US or Canada
- watching
-
if the current member choose to watch and event for open spot notifications, their response will be waitlist and watching will be true
Examples
RSVP 'yes' to the event with id 12345.
curl https://api.meetup.com/2/rsvp/
-F 'event_id=12345'
-F 'rsvp=yes'
-F 'key=YOURKEY'
RSVP 'yes' to the event with id 12345 answering survey questions.
First get the survey questions for the target event
curl 'https://api.meetup.com/2/event/12345/?key=YOURKEY&fields=survey_questions'
Then answer questions accordingly
curl https://api.meetup.com/2/rsvp/
-F 'event_id=12345'
-F 'rsvp=yes'
-F 'answer_123=answering question 123'
-F 'answer_456=answer question 456'
-F 'key=YOURKEY'
everywhere comments