Yelp reference
Every Yelp operation, from the registry
7 operations wired in the registry, 7 of them proven by real traffic.
Choose a Yelp operation
Start with the object your task needs. The groups below use the current catalogue; open an endpoint to check accepted identifiers, filters, price and availability before retrieving.
Other operations
- Yelp business — One Yelp business record.
- Yelp business menu — The menu of a Yelp business in sections with prices, when one is published.
- Yelp business photos — Photos and videos of a Yelp business, twenty per page, with the category counts.
- Yelp related businesses — Businesses the platform recommends alongside one business.
Reviews and offers
- Yelp business reviews — Reviews of a Yelp business, ten per page, with the author profile, votes, photos and any owner reply.
Search and discovery
- Yelp business search — Businesses matching a query near a place, twenty per page, with rating, review count, price range, contact details and coordinates.
- Yelp search suggestions (businesses) — PARTIAL: business suggestions for a typed query near a place (name, id, URL, rating, address), from the held listing's search. The platform's own typeahead rows for categories, common terms and chains are not served; the answer lists what is missing.
Check fields and collection limits
Use the endpoint’s declared parameters and returned continuation. Filters from another platform do not automatically apply here. Preserve source identifiers, URLs and warnings; a successful page does not establish complete history. Published response schemas identify whether they come from a reviewed shaper or observed response shapes.
Agents can use get_endpoint for the current contract and get_docs with topic platforms/yelp to read this page. The coverage guide explains nulls and partial results, and the production guide covers budgets and recovery.
Operations
Yelp
Each row is a registry operation: expand it for parameters, a curl built from the registry's own examples, and a Markdown copy of the whole entry. The badge on the right is the operation's state, read at request time — we publish all three rather than rounding up. Recorded proof is historical, not a guarantee of current availability.
- live · proven
- a real upstream response has been served through this API and recorded
- wired · unproven
- a real-data route is registered, but qualifying proof is absent; permission or capacity restrictions may apply
- sample · free
- no live upstream — /v1 refuses it, /sandbox returns a marked sample
Yelp
7 operationsElsewhere
The same registry, other shapes
- Yelp overview — supported data categories and use cases for this platform.
- Full endpoint reference — every platform on one page.
/openapi.jsonor/openapi.yaml— the machine-readable contract, for Postman, Insomnia or a client generator.GET /v1/utility/endpoints?platform=yelp— the same rows to your code at runtime, for 0 credits.