Get a restaurant's popular dishes and engagement indicators
View all Yelp Business, Reviews & Restaurant Data endpoints →Request popular dishes for one Yelp restaurant identified by its business alias, 22-character business ID or Yelp business URL. The optional integer limit caps the requested number of dishes, accepts 1-50 and defaults to 20. This is a selected-restaurant dish lookup, not a restaurant search or a complete-menu request. The documentation describes dish names with rating, review count, photo count, price and photos. No populated response was independently verified for this operation, and the available example is an empty object. Treat those as documented data concepts rather than confirmed JSON property names or guaranteed populated fields. Availability, ordering, response envelope and missing-value behavior are not established by the available evidence. Use ratings and review or photo counts as engagement indicators, not as orders, revenue or sales rankings. Dish prices need current verification; popular dishes may not match the current menu or offerings at another branch. Compare with separately retrieved menu data and review uncertain name matches manually.
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/popular-dishes API Response (JSON)
{} curl -X GET 'https://api.opendata-api.com/api/project/yelp/popular-dishes?key=<API_KEY>&business=gary-danko-san-francisco&limit=20'
Query Result
Use Cases
- Create a selected-restaurant dish shortlist for an editor to review using documented ratings and engagement counts when present.
- Compare highlighted dish names with a separately retrieved menu and send ambiguous matches for manual reconciliation.
- Choose candidate dishes for a restaurant discovery article without presenting review or photo counts as order volumes.
- Flag documented dish prices for current-price checks before publishing branch-specific dining recommendations.
Frequently asked questions
Does this operation return a complete restaurant menu?
No. Its documented purpose is to retrieve a restaurant's popular dishes. Use a separate menu lookup for menu coverage, and do not assume every highlighted dish is currently offered.
How do I identify the restaurant?
Provide the required business parameter as a Yelp alias, 22-character business ID or Yelp business URL. The documented example alias is gary-danko-san-francisco. Select the intended branch rather than assuming dishes apply across a chain.
How many popular dishes can I request?
The optional integer limit accepts 1-50 and defaults to 20. It is a maximum number requested, not a promise that the restaurant has that many dish records.
Which dish response fields are verified?
No populated response was independently verified for this operation; the available example is empty. Documentation describes dish names, rating, review count, photo count, price and photos, but exact JSON property names, the response envelope and missing-value behavior are not confirmed.
Do popular-dish counts measure sales or orders?
No sales or order-volume fields are documented. Treat dish ratings and review or photo counts as engagement indicators only, not as revenue, order totals or a verified sales ranking.
Can I publish a dish price without checking the current menu?
The documentation mentions dish prices, but price freshness and current branch availability were not verified. Compare with a separately retrieved menu or other current information, and manually review uncertain dish-name matches before publication.