/meetup/groups/search

POST /api/meetup/groups/search

Price: 10 credits

Search Meetup groups by keyword and location with filters for search radius and category. Returns a paginated list of groups with name, description, member count, rating, location and photo.

How to use it

Search Meetup groups (communities). Provide a location (country--state--city like 'us--ca--San Francisco', a city name, or a postal code) and/or a keyword. Filter by distance (miles from the location) and category. Set count to how many groups you want. Each item includes name, description, member_count, rating, city and alias; use meetup/groups with the alias for the full group profile.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• keyword string nullable — Full-text search query (examples: "python")
• location string nullable — Location to search in: country--state--city, a city name, or a postal code (examples: "us--ca--San Francisco", "New York", "94101")
• count integer required — Max number of results to return (min: 1)
• distance string nullable — Search radius from the location, in miles (one of: "2", "5", "10", "25", "50", "100")
• category string nullable — Filter by group category (one of: "art_culture", "beliefs_religion", "career_business", "community_environment", "dancing", "science_education", "games", "health_wellbeing", "identity_language", "music", "travel_outdoor", "parents_family", "pets_animals", "social_activities", "sports_fitness", "technology", "writing")

Response

• @type string (default: "MeetupGroup")
• id string required
• alias string required
• name string required
• description string nullable
• member_count integer nullable
• leader_count integer nullable
• rating number nullable
• rating_count integer nullable
• city string nullable
• state string nullable
• country string nullable
• lat number nullable
• lon number nullable
• timezone string nullable
• is_private boolean (default: false)
• is_new_group boolean nullable
• join_mode string nullable
• founded_at string nullable
• welcome_blurb string nullable
• image string nullable
• category object nullable
  • @type string (default: "MeetupTopic")
  • id string required
  • name string required
  • alias string nullable
• topics array (default: [])
  • @type string (default: "MeetupTopic")
  • id string required
  • name string required
  • alias string nullable
• organizer object nullable
  • @type string (default: "MeetupMember")
  • id string required
  • name string nullable
  • image string nullable
  • is_super_organizer boolean (default: false)
• pro_network object nullable
  • @type string (default: "MeetupProNetwork")
  • id string required
  • name string nullable
  • alias string nullable
  • image string nullable
  • group_count integer nullable
• social_networks array (default: [])
  • @type string (default: "MeetupSocialNetwork")
  • service string required
  • url string required
• upcoming_event_count integer nullable
• past_event_count integer nullable
• source_url string nullable

Errors

• 422 — The request body did not validate Check the fields against this schema. A URN with the wrong prefix is the most common cause.
• 408 — The request ran past its time limit Raise `timeout` in the request body, up to the maximum this endpoint documents. Lowering `count` or turning off the `with_*` flags also helps, because less work finishes sooner.
• 412 — The entity was not found, or a precondition failed Retrying will not help: either the entity does not exist, or the input points at a different one.
• 429 — Too many requests: a rate limit or a usage window is exhausted When the response carries an X-Retry-After header, wait that many seconds and retry: the same number is in the body as `detail.retry_after`, and the limit clears once that window passes. The message in the body names the limit that was hit.
• 500 — Something broke on our side Retrying will not help. If it keeps happening, send us the X-Request-ID from the response headers.
• 529 — Rate limit reached, or the endpoint is overloaded Wait at least 30 seconds, then retry.

Response headers

• X-Error — Error message text (present only on error)
• X-Request-ID — Unique request identifier
• X-Execution-Time — Execution time in seconds
• X-Result-Count — How many records the body carries. 0 means an empty result, which is a normal answer and not by itself an error. A non-zero count can come back together with X-Error when the failure happened partway through — read this header and X-Error independently.
• X-Total-Available-Results — How many records exist for this query, when the endpoint can say. On a `dry_run` request this is the answer and the body is empty. It saturates: the endpoint's documented maximum means 'at least that many', any smaller number is exact.
• X-Warning — Present when the request body carried keys this endpoint does not document. They were ignored, so any filter you meant to apply through them did not apply. Check the spelling against this schema and retry.
• X-Retry-After — Seconds to wait before retrying. Present only on 429.