JustSERPDocs
Eventbrite

Eventbrite search

A page of events from an Eventbrite search or browse page, 20 to a page: dates in the event's timezone, venue with address and coordinates, image, category and tags.

GET
/v1/eventbrite/search

A page of events from an Eventbrite search or browse page, 20 to a page: dates in the event's timezone, venue with address and coordinates, image, category and tags. price and organizer are on the event's page (/v1/eventbrite/event); they are filled here only for promoted events. A search for words with no event is answered with the city's events in general.

Authorization

headerX-API-Key<token>

Your API key.

Query Parameters

cancel_token?string

A name you make up for this request (a UUID is fine), so you can later GET /v1/cancel with it. Only you know it, so only you can cancel. Use a new one for every request, retries included: a cancelled token stays cancelled for a few minutes.

Length1 <= length <= 128
query?string

Words to search for. Not with category.

Lengthlength <= 100
category?string

An Eventbrite category: music, food-and-drink, business, health, ...

location?|

"Austin, TX", "London, United Kingdom" or an Eventbrite place slug (tx--austin, online, united-states). Required unless url.

date?string

With a category or alone; for a query use start_date/end_date.

Value in"today""this_weekend""next_week""this_month"
start_date?string
Match^\d{4}-\d{2}-\d{2}$
end_date?string
Match^\d{4}-\d{2}-\d{2}$
price?"free"

Alone: no query, category or dates.

Value in"free"
page?integer
Range1 <= value <= 100
Default1
url?string

An Eventbrite search page (/d/... or /b/...); the other fields are then unused.

country?string

Two letters, any case (us, GB).

Match^[A-Za-z]{2}$

Response Body

The answer.

application/json
  1. response

The first three keys of every parsed 200 (the answer is the document itself, no success/data envelope): what the search was (search_metadata), what it asked (search_parameters), the parser's own search_information ({} when it has none). The engine's blocks follow, at the same level. An engine whose answer is a list puts it under results.

search_metadata*
search_parameters*

The request's own fields as sent, engine first, without cancel_token.

search_information*

The parser's own, e.g. yelp_search's; otherwise {}.

events_results*array<>

The page's 20 organic events, then any promoted ones (promoted: true, position: null), so a page can hold more than 20.

related_searches?array<>
pagination*
Example Request
curl -X GET 'https://api.justserp.com/v1/eventbrite/search?query=jazz&location=Austin%2C+TX&page=1'
Example Response
{  "search_metadata": {    "id": "string",    "status": "Success",    "created_at": "string",    "request_url": "string",    "html_url": "string"  },  "search_parameters": {},  "search_information": {},  "events_results": [    {}  ],  "related_searches": [    {}  ],  "pagination": {}}