Eventbrite event search
Eventbrite events in a place (or online) by keywords, or by category, event format, date window (or a custom start_date/end_date range, which also works with keywords) and free events, 20 a page: id, name, summary, link, start and end, timezone, online and cancelled flags, series, category, subcategory, format, tags, free flag, price range, sold-out flag, urgency signals, venue (address, coordinates), organizer (followers) and image; plus promoted events. Pass next_page back as page.
Every response includes credits_used: the credits this call cost.
Parameters
| name | type | description |
|---|---|---|
location | string | The site's place slug: ny--new-york, ca--san-francisco, united-kingdom--london, germany--berlin, or online (default). Example: ny--new-york |
q | string | Keywords (alone: not combined with category, format, date or free; start_date/end_date may be added). Example: jazz |
category | business | food-and-drink | health | music | auto-boat-and-air | charity-and-causes | community | family-and-education | fashion | film-and-media | hobbies | home-and-lifestyle | arts | government | spirituality | school-activities | science-and-tech | holiday | sports-and-fitness | travel-and-outdoor | other | Event category (with a date window or start_date/end_date). |
date | today | tomorrow | this-weekend | this-week | next-week | this-month | next-month | Date window. |
free | string | 1 = free events only. |
format | classes | conferences | seminars | conventions | expos | festivals | performances | screenings | galas | parties | networking | races | tournaments | games | tours | attractions | retreats | appearances | Event format (combines with category, date and free; not with q). |
start_date | string | Custom date range start, YYYY-MM-DD (with end_date; instead of date). |
end_date | string | Custom date range end, YYYY-MM-DD (with start_date). |
page | integer | Page number (default 1). Pass next_page back; null on the last page. |
Every endpoint also takes fresh, raw, fields (see lean responses and caching).
Example
curl "https://api.api.sh/eventbrite/v1/search?location=ny--new-york" \
-H "x-api-key: $APISH_KEY" import os, requests
res = requests.get(
"https://api.api.sh/eventbrite/v1/search",
params={"location": "ny--new-york"},
headers={"x-api-key": os.environ["APISH_KEY"]},
timeout=120,
)
res.raise_for_status()
data = res.json() const url = new URL("https://api.api.sh/eventbrite/v1/search");
url.searchParams.set("location", "ny--new-york");
const res = await fetch(url, { headers: { "x-api-key": process.env.APISH_KEY } });
if (!res.ok) throw new Error(`${res.status} ${await res.text()}`);
const data = await res.json(); Response
A JSON object with the fields described above, plus raw (the source's own data), cached, fetched_at and credits_used. Errors return {"success": false, "error": "…"} with the HTTP status (see errors). A lookup that ran but found nothing (404) costs the price above; refused calls and errors on our side are free (what's charged).