/eventbrite/events/search

POST /api/eventbrite/events/search

Price: 20 credits

Search Eventbrite events by location, keyword, category, price, date, and language. Returns a paginated list of events, each with id, name, summary, url, cover image, start and end date/time with timezone, online flag, category, subcategory and format, tags, sales status, venue with address and coordinates, organizer (with follower count and social links), and price range. Use the domain parameter to select the country marketplace and the currency parameter to display prices in a specific currency.

How to use it

Search Eventbrite events within a location (city slug such as ny--new-york, or online). Optionally filter by keyword, category, price (free/paid), date (today/tomorrow/this_weekend, or a custom date_from/date_to range as YYYY-MM-DD), and language, and set currency to display prices in. Set count to how many results you want. Each item has id, name, summary, url, image + images, start_at/end_at (unix seconds, UTC) plus start_local/end_local and timezone, is_online, category, subcategory, format, tags, sales_status, venue (name, address, city, region, country, postal_code, latitude, longitude), organizer (id, name, url, image, summary, follower_count, twitter, facebook, website), and price (min_price, max_price, currency, is_free). Use the domain parameter to select the country marketplace.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• domain string — Eventbrite marketplace domain (country site). (default: "eventbrite.com"; one of: "eventbrite.com", "eventbrite.com.ar", "eventbrite.com.au", "eventbrite.at", "eventbrite.be", "eventbrite.com.br", "eventbrite.ca", "eventbrite.cl", "eventbrite.co", "eventbrite.dk", "eventbrite.fi", "eventbrite.fr", "eventbrite.de", "eventbrite.hk", "eventbrite.ie", "eventbrite.it", "eventbrite.com.mx", "eventbrite.nl", "eventbrite.co.nz", "eventbrite.com.pe", "eventbrite.pt", "eventbrite.sg", "eventbrite.es", "eventbrite.se", "eventbrite.ch", "eventbrite.co.uk")
• location string required — Location to search within — an Eventbrite city slug such as ny--new-york or il--chicago, or online for virtual events. (examples: "ny--new-york", "il--chicago", "online"; minLength: 1)
• keyword string nullable — Optional free-text search keyword
• category string nullable — Optional event category filter (one of: "music", "business", "food-and-drink", "community", "performing-and-visual-arts", "film-and-media", "sports-and-fitness", "health", "science-and-tech", "travel-and-outdoor", "charity-and-causes", "spirituality", "family-and-education", "holiday", "government", "fashion", "home-and-lifestyle", "auto-boat-and-air", "hobbies", "school-activities", "other")
• price string nullable — Optional price filter — free or paid events only (one of: "free", "paid")
• date string nullable — Optional relative date filter (today, tomorrow, this weekend); use date_from/date_to for a custom range (one of: "today", "tomorrow", "this_weekend")
• language string nullable — Optional event language filter (one of: "en", "de", "es", "fr", "it", "nl", "pt", "sv")
• currency string nullable — Optional currency to display event prices in (one of: "USD", "CAD", "EUR", "GBP", "JPY", "AUD", "NZD", "CHF", "HKD", "SGD", "SEK", "DKK", "PLN", "NOK", "HUF", "CZK", "MXN", "ILS", "ARS", "BRL", "CLP", "MYR", "PHP", "TWD", "THB", "TRY")
• date_from string nullable — Optional start of a custom date range (YYYY-MM-DD) (examples: "2026-08-01")
• date_to string nullable — Optional end of a custom date range (YYYY-MM-DD) (examples: "2026-08-31")
• count integer required — Max number of results to return (min: 1)

Response

• @type string (default: "EventbriteSearchEvent")
• id string required
• name string required
• summary string nullable
• url string required
• image string nullable
• images array (default: [])
• start_at integer nullable
• end_at integer nullable
• start_local string nullable
• end_local string nullable
• timezone string nullable
• is_online boolean nullable
• category string nullable
• subcategory string nullable
• format string nullable
• tags array (default: [])
• sales_status string nullable
• venue object nullable
  • @type string (default: "EventbriteVenue")
  • id string nullable
  • name string nullable
  • address string nullable
  • city string nullable
  • region string nullable
  • country string nullable
  • postal_code string nullable
  • latitude number nullable
  • longitude number nullable
• organizer object nullable
  • @type string (default: "EventbriteOrganizerRef")
  • id string nullable
  • name string nullable
  • url string nullable
  • image string nullable
  • summary string nullable
  • follower_count integer nullable
  • twitter string nullable
  • facebook string nullable
  • website string nullable
• price object nullable
  • @type string (default: "EventbritePrice")
  • min_price number nullable
  • max_price number nullable
  • currency string nullable
  • is_free 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.