Container Get

Parameters: Normal authorization parameters are required. The output may be adjusted as normal with format, as well as a fields specifier:

• fields Request that additional fields (separated by commas) be included in the output.

• id The ID of the container
• name The name of the container
• meetup_url User-facing URL for this container on Meetup
• urlname URL path to the container, as in http://www.meetup.com/<urlname> (no slashes)
• description Container description
• time Fixed time for all events in this container, in milliseconds since the epoch
• scheduling Set to "open", "date", or "datetime" to indicate that events should occur on any date, a specific date, or a specific date and time. API clients are encouraged but not required to follow this recommended use of the time field.
• link URL associated with this container, usually off-site
• link_name Name of the resource at link
• facebook_urlname Facebook page associated with this container
• twitter_urlname Twitter account name associated with this container
• meetup_count Count of upcoming and pending Meetups in this container. Only included if requested in the fields parameter.
• past_meetup_count Count of past Meetups in this container. Only included if requested in the fields parameter.
• member_count Count of unique members who have rsvp'd to a meetup in this container. Only included if requested in the fields parameter.
• countries List of two-letter country codes where Meetups have been scheduled in this container. Only included if requested in the fields parameter.
• created Container created time, in milliseconds since the epoch
• updated Container updated time, in milliseconds since the epoch
• founder Founder for this container
  • member_id
  • name
  • member_city if requested through the fields parameter
  • member_country if requested through the fields parameter
  • member_state if requested through the fields parameter
• theme Custom appearance for this container, if any
  • pageback_color HTML hex color code
  • boxback_color
  • button_color
  • link_color
  • banner_link URL of the page banner, if any
  • banner_height Banner height in pixels. All banners are 960 pixels wide.
• udf_<varname> Any User defined fields specified in the fields parameter

Container Edit

Parameters: All parameters are optional, will update the container when provided. You must be authenticated as the founder, and this method requires an HTTP POST.

• name renames the container if the requested name is available
• description
• link must be a URL
• link_name
• facebook_urlname path name without slashes
• twitter_urlname account name, no slash or @
• time set suggested event date / datetime, in milliseconds since the epoch or 0 to clear
• scheduling Set to "open", "date", or "datetime" to indicate that events should occur on any date, a specific date, or a specific date and time. API clients are encouraged but not required to follow this recommended use of the time field.
• udf_<varname> modify or add user defined values
• fields Request that additional fields (separated by commas) be included in the output.

If successful, this method returns a 200 OK response. The content body is the same as that returned by Container Get.

Container Create

Parameters: the required name parameter must be supplied with the request. This method requires an HTTP POST.

• name Name of this container
• description
• link must be a URL
• link_name
• facebook_urlname path name without slashes
• twitter_urlname account name, no slash or @
• time suggested event date / datetime, in milliseconds since the epoch
• scheduling Set to "open", "date", or "datetime" to indicate that events should occur on any date, a specific date, or a specific date and time. API clients are encouraged but not required to follow this recommended use of the time field.
• udf_<varname> user defined values
• fields Request that additional fields (separated by commas) be included in the output.

If successful, this method returns a 201 Created response with a Location header containing the Container Get method for this container. The content body is the same as that returned by Container Get.

Containers Query

Parameters: at least one of the required parameter(s) must be supplied with the request.

• container_id ID of the container
• urlname URL path to the container, as in http://www.meetup.com/<urlname> (no slashes)
• link External URL associated with the container
• udf_<varname> Query by any user defined parameter
• fields Request that additional fields (separated by commas) be included in the output.

Ordering:

• time Name of the container

Each item in the results list for a JSON or XML request will contain the fields listed in Container Get.

Alerts Get

Parameters: No parameters are required or considered other than for authorization and format.

Response item includes properties for the authenticated user's alerts by category. These are enabled at the container level, but sent only for events the user has rsvpd to. If the authenticated user has not subscribed to alerts for the container, a 404 response is returned.

• comments Alert for each comment, "true" or "false"
• rsvps Alert for each rsvp, "true" or "false"
• updates Alert for updates to events, "true" or "false"

Alerts Edit

Parameters: All parameters are optional, updates alerts for the authenticated user. This method requires an HTTP POST.

• comments Alert for each comment, "true" or "false"
• rsvps Alert for each rsvp, "true" or "false"
• updates Alert for updates to events, "true" or "false"

If successful, this method returns a 200 OK response. The content body is the same as that returned by Alerts Get. If a 404 response is returned, the user has not subscribed to any alerts for this container and should rsvp to an event first.

Community Get

Parameters: Normal authorization parameters are required. The output may be adjusted as normal with format, as well as a fields specifier:

• fields Request that additional fields (separated by commas) be included in the output.

• id The ID of the community
• name Name of the community
• urlname URL path to the community, as in http://www.meetup.com/<container_urlname>/<urlname> (no slashes)
• meetup_url User-facing URL for this community on Meetup
• city Community city
• state State or province
• zip Zip or postal code
• country Community country
• lat, lon Latitude and longitude coordinates of the community
• created Community created time, in milliseconds since the epoch
• updated Community updated time, in milliseconds since the epoch
• meetup_count Count of upcoming and pending Meetups in this community. Only included if requested in the fields parameter.
• past_meetup_count Count of past Meetups in this community. Only included if requested in the fields parameter.
• container Container for this community
  • id
  • name
  • urlname
• udf_<varname> Any User defined fields specified in the fields parameter

Community Edit

Parameters: All parameters are optional, will update the community when provided. This method requires an HTTP POST.

• name Name of the community
• city Community city
• state State or province
• zip Zip or postal code
• country Community country
• lat, lon Latitude and longitude coordinates of the community

If successful, this method returns a 200 OK response. The content body is the same as that returned by Community Get.

Community Create

Parameters: An identifier for the container is required as well at least one location parameter set. Other location details may be filled out automatically. This method requires an HTTP POST.

• container_id May serve as the required identifier of the container
• urlname May serve as the required identifier of the container
• lat, lon May serve as the required location parameter set.
• country, city May serve as the required location parameter set. Country and city. For the US, state is also required
• zip A US zip or Canadian postal code. May serve as the required location parameter set.
• name Name of the community

If successful, this method returns a 201 Created response with a Location header containing the Community Get method for this community. The content body is the same as that returned by Community Get.

Communities Query

Parameters: at least one of the required parameter(s) must be supplied with the request.

• container_id One or more IDs, separated by commas
• urlname Up to five URL paths, separated by commas
• community_id One or more IDs, separated by commas
• community_urlname Up to five URL paths, separated by commas. urlname or container_id is also required
• lat, lon Coordinates to search near.
• country, city Country and city. For the US, state is also required
• zip A US zip or Canadian postal code
• udf_<varname> user defined values
• fields Request that additional fields (separated by commas) be included in the output.

Ordering:

• name Community name

Each item in the results list for a JSON or XML request will contain the fields listed in Community Get.

Community Followed Get

Parameters: No parameters are required other than for authorization and format.

• fields Request that additional fields (separated by commas) be included in the output.

• id The ID of the community
• status "member" or "helper", if member has helped plan an event in the corresponding community
• created created time, in milliseconds since the epoch
• member Member following community
  • member_id
  • name
  • member_city if requested through the fields parameter
  • member_country if requested through the fields parameter
  • member_state if requested through the fields parameter
• container Container for this community
  • id
  • name
  • urlname
• community Community for this follow
  • id
  • name
  • urlname
• udf_<varname> User defined fields specified in the fields parameter

Community Follow Delete

Parameters: No parameters are required or considered other than for authorization and format. This method requires an HTTP DELETE.

If successful, this method returns a 200 OK response. The content body includes a success message.

Community Follow Create

Parameters: at least one of the required parameter(s) must be supplied with the request. The follow is always applied for the current authenticated member. This method requires an HTTP POST.

• community_id ID of the community to follow.
• udf_<varname> user defined values
• fields Request that additional fields (separated by commas) be included in the output.

If successful, this method returns a 201 Created response with a Location header containing the Community Followed Get method for this event. The content body is the same as that returned by Community Followed Get.

Communities Followed Query

Parameters: No parameters are required. If no parameters are provided, then all communities followed by the authenticated user will be included in the response.

• container_id One or more IDs, separated by commas
• urlname Up to five URL paths, separated by commas
• community_id One or more IDs, separated by commas
• udf_<varname> User defined fields
• fields Request that additional fields (separated by commas) be included in the output.

Ordering:

• name Community name

Each item in the results list for a JSON or XML request will contain the fields listed in Community Follow Get.

Event Get

Parameters: Normal authorization parameters are required. The output may be adjusted as normal with format, as well as a fields specifier:

• fields Request that additional fields (separated by commas) be included in the output.

• id The ID of the event
• time Start time of the event in milliseconds since the epoch, if set
• meetup_url User-facing URL for this event on Meetup
• short_description Event short description.
• description Event description.
• title The title of the event. This field is not currently displayed by the Meetup Everywhere front-end, but may be useful in custom integrations.
• venue_name Name of the place where the event will happen
• address1 The street address, if assigned
• city Event city
• state State or province
• zip Zip or postal code
• country Event country
• lat, lon Latitude and longitude coordinates of the event
• status "past", "pending" (no date), or "upcoming"
• link Link associated with the event. Displayed on the event page, and users are prompted to follow this link after indicating interest.
• created Event created time, in milliseconds since the epoch
• updated Event updated time, in milliseconds since the epoch
• container Container for this event
  • id
  • name
  • urlname
• community Community for this event
  • id
  • name
  • urlname
• helpers Helpers who planned this event, if any
  • member_id
  • name
  • member_city if requested through the fields parameter
  • member_country if requested through the fields parameter
  • member_state if requested through the fields parameter
• rsvp_count Current number of rsvps, included only if requested with the fields parameter.
• udf_<varname> Any User defined fields specified in the fields parameter

Event Edit

Parameters: All parameters are optional, will update the event when provided. This method requires an HTTP POST.

• short_description Event short description.
• description
• title The title of the event. This field is not currently displayed by the Meetup Everywhere front-end, but may be useful in custom integrations.
• venue_name Name of the place where the event will happen
• address1 street address; specify an empty string if you want to prevent this from being inferred from other parameters
• country, city, state
• zip Zip or postal code.
• lat, lon
• time event start time in milliseconds since the epoch
• local_time Alternative to the time parameter for applications that can not easily calculate an event's UTC time. If you know the wall-clock time and location for an event but do not know its UTC offset, you can supply a local_time and Meetup will apply the appropriate offset. The format for this parameter is milliseconds since the epoch as if the event occurred in a UTC zone.
• link Link associated with the event. Displayed on the event page, and users are prompted to follow this link after indicating interest.
• udf_<varname> modify or add user defined values
• fields Request that additional fields (separated by commas) be included in the output.

If successful, this method returns a 200 OK response. The content body is the same as that returned by Event Get.

Event Create

Parameters: An identifier for the community is required as well at least one location parameter set. Other location details may be filled out automatically. This method requires an HTTP POST.

• community_id May serve as the required identifier of the event community
• container_id and community_urlname May serve as the required identifier of the event community
• urlname and community_urlname May serve as the required identifier of the event community (urlname is the container urlname)
• lat, lon May serve as the required location parameter set.
• country, city May serve as the required location parameter set. Country and city. For the US, state is also required
• zip A US zip or Canadian postal code. May serve as the required location parameter set.
• address1 street address; specify an empty string if you want to prevent this from being inferred from other parameters
• short_description Event short description.
• description
• time event start time in milliseconds since the epoch. If the container has a default time value it will be used when no time is supplied, otherwise the event will be created without a time.
• local_time Alternative to the time parameter for applications that can not easily calculate an event's UTC time. If you know the wall-clock time and location for an event but do not know its UTC offset, you can supply a local_time and Meetup will apply the appropriate offset. The format for this parameter is milliseconds since the epoch as if the event occurred in a UTC zone.
• title The title of the event. This field is not currently displayed by the Meetup Everywhere front-end, but may be useful in custom integrations.
• venue_name Name of the place where the event will happen
• link Link associated with the event. Displayed on the event page, and users are prompted to follow this link after indicating interest.
• udf_<varname> user defined values
• fields Request that additional fields (separated by commas) be included in the output.

If successful, this method returns a 201 Created response with a Location header containing the Event Get method for this event. The content body is the same as that returned by Event Get.

Events Query

Parameters: at least one of the required parameter(s) must be supplied with the request.

• event_id ID of an event
• container_id One or more IDs, separated by commas
• urlname Up to five URL paths, separated by commas
• community_id One or more IDs, separated by commas
• community_urlname Up to five URL paths, separated by commas. urlname or container_id is also required
• lat, lon Coordinates to search near.
• country, city Country and city. For the US, state is also required
• zip A US zip or Canadian postal code
• before Return events scheduled before the specified date, formatted as described below
• after Return events scheduled after the specified date, formatted as described below
• status Return events matching one of the given status values, separated by commas. Possible statuses are "pending", "upcoming", and "past". The default status parameter is "past,pending,upcoming".
• udf_<varname> user defined values
• fields Request that additional fields (separated by commas) be included in the output.

Date Formatting: Parameters for dates can be specified in absolute or relative terms. Absolute dates are specified in numbers only: MMDDYYYY. Relative dates are specified in days (d), weeks (w), or months (m) before or after today. Tomorrow is "1d", yesterday is "-1d"; three weeks from now is "3w", and six months ago is "-6m". These can be used with after and before to define a time window in a static request that advances with the actual date.

Ordering:

• time Event date and time

Each item in the results list for a JSON or XML request will contain the fields listed in Event Get.

RSVP Get

Parameters: No parameters are required other than for authorization and format.

• fields Request that additional fields (separated by commas) be included in the output.

• id The ID of the rsvp
• event_id The ID of the event
• created rsvp created time, in milliseconds since the epoch
• member Member that rsvp'd
  • member_id
  • name
  • member_city if requested through the fields parameter
  • member_country if requested through the fields parameter
  • member_state if requested through the fields parameter

RSVP Delete

Parameters: No parameters are required or considered other than for authorization and format. This method requires an HTTP DELETE.

If successful, this method returns a 200 OK response. The content body includes a success message.

RSVP Create

Parameters: at least one of the required parameter(s) must be supplied with the request. The RSVP is always applied for the current authenticated member. This method requires an HTTP POST.

• event_id ID of the event to rsvp to.
• udf_<varname> user defined values
• fields Request that additional fields (separated by commas) be included in the output.

If successful, this method returns a 201 Created response with a Location header containing the RSVP Get method for this event. The content body is the same as that returned by RSVP Get.

RSVPs Query

Parameters: at least one of the required parameter(s) must be supplied with the request, and multiple query values may be separated with commas.

• event_id ID of an event
• member_id ID of a member
• udf_<varname> User defined fields
• fields Request that additional fields (separated by commas) be included in the output.

Ordering:

• time RSVP date and time

Each item in the results list for a JSON or XML request will contain the fields listed in RSVP Get.

Comment Get

Parameters: No parameters are required other than for authorization and format.

• fields Request that additional fields (separated by commas) be included in the output.

• id ID of the comment
• parent_id ID of the parent comment, if comment is threaded
• comment content of the comment
• event_id ID of the event
• created comment created time, in milliseconds since the epoch
• member Member that commented
  • member_id
  • name
  • member_city if requested through the fields parameter
  • member_country if requested through the fields parameter
  • member_state if requested through the fields parameter

Comment Delete

Parameters: No parameters are required or considered other than for authorization and format. This method requires an HTTP DELETE.

If successful, this method returns a 200 OK response. The content body includes a success message.

Comment Create

Parameters: at least one of the required parameter(s) must be supplied with the request. The comment is always entered for the current authenticated member. This method requires an HTTP POST.

• event_id ID of the event to comment on
• comment comment content
• parent_id ID of parent comment to thread
• udf_<varname> user defined values
• fields Request that additional fields (separated by commas) be included in the output.

If successful, this method returns a 201 Created response with a Location header containing the Comment Get method for this event. The content body is the same as that returned by Comment Get.

Comments Query

Parameters: at least one of the required parameter(s) must be supplied with the request, and multiple query values may be separated with commas.

• container_id one or more container IDs
• urlname one or more container urlnames
• community_id One or more IDs, separated by commas
• community_urlname Up to five URL paths, separated by commas. urlname or container_id is also required
• event_id one or more event IDs
• member_id one or more member IDs
• comment_id one or more comment IDs
• parent_comment_id one or more parent comment IDs
• udf_<varname> User Defiened fields
• fields Request that additional fields (separated by commas) be included in the output.

Ordering:

• time Comment date and time

Each item in the results list for a JSON or XML request will contain the fields listed in Comment Get.

To make it easy to develop Meetup Everywhere applications that have little or no local storage, the API supports user defined fields for Containers, Events, RSVPs and Comments. These field names begin with "udf_" followed by a name you choose, and may be assigned any string value.

User defined fields are assigned and queried just as other fields in the API. Include a parameter beginning with "udf_" in a create or edit POST method to assign it as a field. Field names may be up to 35 characters including the "udf_" prefix. For query methods, specify a UDF parameter with a value to limit the results to those that contain that field with a matching value. The match is case-insensitive and no wildcards are supported.

In result items, these fields are returned only when specified in the fields parameter of the request. Specify "all_udf" to retrieve any fields associated with the entity.