JustSERPDocs
Eventbrite

Eventbrite event

One Eventbrite event: title, full description, start and end (local and UTC), venue or online, organizer, ticket price range and availability, sales status, refund policy, age restriction, FAQs, agenda, images.

GET
/v1/eventbrite/event

One Eventbrite event: title, full description, start and end (local and UTC), venue or online, organizer, ticket price range and availability, sales status, refund policy, age restriction, FAQs, agenda, images.

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
event_id?string

The number at the end of the event's address.

Match^\d{6,20}$
url?string

The event page, eventbrite./e/...

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 {}.

event_results*
Example Request
curl -X GET 'https://api.justserp.com/v1/eventbrite/event?event_id=2002840255118'
Example Response
{  "search_metadata": {    "id": "string",    "status": "Success",    "created_at": "string",    "request_url": "string",    "html_url": "string"  },  "search_parameters": {},  "search_information": {},  "event_results": {}}