Search Yelp events by city, category and date range

View all Yelp Business, Reviews & Restaurant Data endpoints →

Browse Yelp event listings with a required city string containing a Yelp Events city slug or events URL. Optionally narrow the request with category, start_date and end_date; request official Yelp events with the string official_only=true; select a sort_by value and page number. Dates use YYYY-MM-DD. The documented defaults are official_only=false, sort_by=popular and page=1. Documentation describes 15 events per page, with venue and start-time information. Page numbers 1 through 100 are documented, but this does not guarantee 100 populated pages or comprehensive coverage of a city's events. No probe response is available for this endpoint, and its supplied HTTP 200 source example is an empty object. Exact event keys, list nesting, identifier fields, types, counts and pagination metadata are unverified. Use the results as a source-specific event shortlist rather than a complete event directory or a ticket-availability feed. A selected event can be inspected with the event-details operation using its event slug or URL; the available example does not establish how that identifier is represented in search results.

API Features

City-slug event discovery Start from a required Yelp Events city slug such as sf, la, nyc or chicago, or supply a Yelp events URL for the city.
Category-focused programming Narrow listings with one of 13 documented event categories, including music, food_and_drink, festivals_and_fairs and kids_and_family.
Date-bounded event windows Set the earliest and latest event dates independently with start_date and end_date in YYYY-MM-DD format for a defined editorial planning window.
Official-event and ordering controls Use official_only as a true or false string and select popular, recently_added or free ordering. The free value is a documented sort choice, not a separate price filter.
Fifteen-entry page selection Select a page from the documented range of 1 to 100, with 15 events described per page. Actual page population and response pagination fields have not been verified.

Live API Demo

GET /api/project/yelp/search-events

Request cost is temporarily unavailable. No price is assumed.

View pricing

API Response (JSON)

{}
curl -X GET 'https://api.opendata-api.com/api/project/yelp/search-events?key=<API_KEY>&city=sf&official_only=false&page=1&sort_by=popular'
📢
Need Help?
If you encounter API issues or need other API requirements, please contact us.
Contact Us

Use Cases

Frequently asked questions

What values does the city parameter accept?

Supply a Yelp Events city slug such as sf, la, nyc or chicago, or a Yelp events URL such as https://www.yelp.com/events/sf. The required city parameter is not documented as a latitude-and-longitude input.

How do the date filters work?

start_date sets the earliest event date and end_date sets the latest event date; both are optional strings in YYYY-MM-DD format. Examples are 2026-10-01 and 2026-10-31. The available evidence does not define boundary inclusivity or timezone handling.

How many events are on a page, and which page numbers are supported?

Documentation describes 15 events per page, a default page of 1 and allowed page numbers from 1 to 100. That range does not imply every page is populated, and response totals or next-page fields have not been verified.

How do I request only official Yelp events?

Set official_only to the string true. The documented default is the string false; this parameter remains a string rather than a boolean in the request contract.

Does sort_by=free guarantee only free events?

No such guarantee is documented. free is one of the allowed sort_by values, alongside popular and recently_added, and popular is the default. Confirm any returned price before describing an event as free.

Which search response fields have been observed?

None have been independently observed for this endpoint. Documentation describes event listings with venue and start-time information, but no probe response is available and the supplied HTTP 200 source example is an empty object. Exact JSON keys, list structure, event identifiers and pagination metadata remain unverified.

Related operations

Guides

View Subscription Plans →