Get Yelp event details by slug or event URL
View all Yelp Business, Reviews & Restaurant Data endpoints →Retrieve the documented details of one Yelp event using the required event string. Supply an event slug, such as huntington-beach-oktoberfest-on-thursdays-4, or a Yelp event URL. This is an individual event lookup, not a city event search. The documented response content covers the event description, start and end times, venue address, price and interested count. These are documentation-level expectations rather than observed response fields: no probe response is available for this endpoint, and its provided HTTP 200 source example is an empty object. Exact JSON keys, nesting, types and field optionality are therefore unverified. Use returned schedule and price information only as supplied; do not infer a missing timezone, currency or ticket availability. Treat an interested count as an interest signal, not confirmed attendance. Event details do not establish that a booking or ticket purchase can be completed.
API Features
Live API Demo
🔒 Sign in to try it live
Log in to call this API with your own API key. New accounts get 100 free credits — no card required.
Log in / Sign upNo active API key found. Create one in your Dashboard, then reload this page. Dashboard →
/api/project/yelp/event-details API Response (JSON)
{} curl -X GET 'https://api.opendata-api.com/api/project/yelp/event-details?key=<API_KEY>&event=huntington-beach-oktoberfest-on-thursdays-4'
Query Result
Use Cases
- Enrich a city-guide detail card after an editor selects an event from a city event listing, using the returned description, schedule and venue address when available.
- Prepare a human-reviewed calendar export from an event's returned start and end values, retaining any timezone information and flagging missing timezone data instead of guessing.
- Assemble an outing brief with the listed venue address and event price, leaving absent cost or currency information unresolved and checking ticket availability separately.
- Prioritize an editorial event-review queue using returned interested counts as interest signals, without labeling them as attendance or ticket-sales totals.
Frequently asked questions
What should I pass in the event parameter?
Pass a Yelp event slug, such as huntington-beach-oktoberfest-on-thursdays-4, or a Yelp event URL. The event parameter is a required string and identifies one event, not a city or venue search.
Which event details are documented, and are their response fields verified?
Documentation describes an event description, start and end times, venue address, price and interested count. No probe response is available, and the supplied HTTP 200 source example is an empty object, so exact JSON keys, types, nesting and optionality are not verified.
Can I assume the schedule includes a timezone and the price includes a currency?
No. Timezone and currency fields are not established by the available example. Preserve any information actually returned and mark missing values unresolved before calendar export or price display.
Does an interested count confirm attendance or available tickets?
No. An interested count should only be used as an interest signal. This event lookup does not establish confirmed attendance, ticket inventory or the ability to purchase a ticket.