/meetup/events/search

POST /api/meetup/events/search

Price: 10 credits

Search Meetup events by keyword and location with filters for online/in-person type, search radius, category and date range. Returns a paginated list of events with title, description, start and end time, venue, hosting group with rating, attendee count, price and photo.

How to use it

Search Meetup events. Provide a location (country--state--city like 'us--ca--San Francisco', a city name, or a postal code) and/or a keyword. Filter by event_type (online / in_person), distance (miles from the location), category, and date (relative range) or start_date/end_date (YYYY-MM-DD). Set count to how many events you want. Each item includes the event and its hosting group; use meetup/events for full details.

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)
• event_type string nullable — Filter by whether the event is online or in person (one of: "online", "in_person")
• distance string nullable — Search radius from the location, in miles (one of: "2", "5", "10", "25", "50", "100")
• category string nullable — Filter by event 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")
• date string nullable — Filter by a relative date range (one of: "today", "tomorrow", "this_week", "this_weekend", "next_week", "next_weekend")
• start_date string nullable — Only events starting on or after this date (YYYY-MM-DD) (examples: "2026-08-01")
• end_date string nullable — Only events starting on or before this date (YYYY-MM-DD) (examples: "2026-08-31")

Response

• @type string (default: "MeetupEvent")
• id string required
• name string required
• description string nullable
• source_url string nullable
• status string nullable
• event_type string nullable
• is_online boolean (default: false)
• start_at string nullable
• end_at string nullable
• created_at string nullable
• venue object nullable
  • @type string (default: "MeetupVenue")
  • name string nullable
  • address string nullable
  • city string nullable
  • state string nullable
  • country string nullable
  • lat number nullable
  • lon number nullable
• max_tickets integer nullable
• going_count integer nullable
• waitlist_count integer nullable
• rsvp_state string nullable
• guests_allowed boolean nullable
• allowed_guest_count integer nullable
• is_free boolean (default: true)
• fee_amount number nullable
• fee_currency string nullable
• topics array (default: [])
  • @type string (default: "MeetupTopic")
  • id string required
  • name string required
  • alias string nullable
• hosts array (default: [])
  • @type string (default: "MeetupEventHost")
  • member_id string required
  • name string nullable
  • image string nullable
  • is_super_organizer boolean (default: false)
• speaker object nullable
  • @type string (default: "MeetupEventSpeaker")
  • name string required
  • bio string nullable
  • image string nullable
• group object nullable
  • @type string (default: "MeetupEventGroup")
  • id string required
  • alias string nullable
  • name string nullable
  • image string nullable
  • timezone string nullable
  • city string nullable
  • state string nullable
  • country string nullable
  • rating number nullable
  • rating_count integer nullable
• image string nullable
• series_description string nullable
• creator_id string nullable
• is_rsvps_closed boolean 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.