Yelp Business, Reviews & Restaurant Data — Try the interactive demo

Retrieve compact information for a supplied list of known Yelp businesses. The required businesses query parameter is one comma-separated string containing up to 20 business aliases, IDs or yelp.com URLs. This is identifier-based enrichment, not a location or city-wide discovery search. The catalog documents rating, phone, website, address, coordinates and photo as returned information. These are documented output concepts, not confirmed JSON field names: no batch response was observed, and the supplied source response example is an empty object. The response envelope, record ordering, representation of unresolved inputs and partial-failure behavior remain unverified. Confirm those details before relying on positional matching in a production import.

Get the profile of one known Yelp business using the required business query parameter. It accepts a business alias, a 22-character business ID or a yelp.com business URL. Select the intended branch before attaching its profile to your own records. An observed successful response was a business object containing id, alias, name, rating and review_count, along with address and contact data, hours, amenities and popular_dishes. The tested Gary Danko profile returned rating 4.5 and review_count 6148; those are sample observations, not fixed values or a freshness guarantee. The catalog also describes phone, website and health-score information, but health-score availability was not established by the observed response summary. The supplied source example additionally includes about, alternate_links and alternate_names. Its visible about fields include history, owner, specialties and year_established; visible address fields include city, country_code, formatted, line1, line2, line3, postal_code and state. The example also shows amenities entries with name and is_available. Those example-specific structures are not independently verified by the probe summary, and the example is incomplete. Do not treat omitted attributes as false or unavailable. A deliberately nonexistent business returned HTTP 404 with an error field, so callers must handle not-found responses separately from a successful profile.

Retrieve the menu associated with one Yelp business. The required business query parameter accepts a business alias, a 22-character business ID or a yelp.com business URL. It selects a specific branch; no menu search, pagination or item-filter parameter is documented for this operation. The observed Golden Boy Pizza response was an object identifying the business, with has_yelp_menu set to true, Yelp and external menu links, and two sections containing six named items with USD prices. The observation establishes that structured, priced menu data can be returned for that business. It does not establish complete menu coverage, price freshness or menu availability for every restaurant. Except for has_yelp_menu, the observation summary does not provide exact JSON key names for the business identity, links, sections or item prices. The catalog additionally describes item descriptions and photos, but the successful observation summary does not confirm those fields. The supplied source response example is an empty object and adds no schema evidence. Inspect the returned menu indicator, links and section data separately; keep structured-item, link-only and unavailable states distinct rather than assuming every business returns a fully parsed menu. Currency and price presentation should follow the actual response, not a universal USD assumption.

Retrieve photo metadata for one Yelp business using its alias, 22-character business ID or Yelp business URL. Optionally select a category alias or filter captions with query. The documented defaults are category=all, page=1 and page_size=30; page accepts 1-1000 and page_size accepts 1-100. Read the returned categories to discover the aliases available for that business. A recorded response for page=1 and page_size=3 contained count=14885 and three photos, not 14885 returned records. Its top-level pagination fields were count, per_page, current_page, total_pages, next and previous. The business object contained id, alias, name and link; categories contained alias, name and photo_count. Each photos record exposed id, an original-size link, thumbnail_link, caption, width, height, uploaded_at, tags, like_count, uploaded_by and review_id. The uploaded_by object exposed id, name, link, location, photo_link, review_count, friend_count, photo_count, elite_year, is_elite and is_elite_all_star. Field presence does not guarantee that every value is populated on other pages or businesses. The documentation also describes a videos category, but video-specific fields were not verified by this photo response. Media links are references, not a grant of download or republication rights. Retain uploader information only as needed for your permitted use.

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.

Retrieve a Yelp business's own posts and announcements by supplying its alias, 22-character business ID or Yelp business URL in the required business parameter. This operation has no documented page, limit or date-filter parameter. It retrieves business-authored updates rather than customer reviews. The documentation describes posts and announcements with photos, links and likes. No populated response was independently verified for this operation, and the available example is an empty object. These are documented content attributes, not confirmed JSON property names or guarantees of populated fields. The response envelope, ordering, posting timestamps, promotion validity dates, completeness and behavior for businesses without posts are not established by the available evidence. Use returned content, when available, as an editorial review queue. Do not treat a promotion or operational announcement as current without checking its applicability; if no validity date is supplied, do not infer one. Likes indicate the documented engagement concept, not a verified count of customers or purchases. Keep business-authored content separate from customer feedback and respect permissions for associated media.

Retrieve a page of Yelp community questions for one known business, with the top answer to each question as described in the endpoint documentation. The required business input accepts a Yelp business alias, a 22-character business ID or a Yelp business URL. The optional integer page defaults to 1, accepts values from 1 through 1000 and is documented as returning 10 questions per page. Documented response content consists of community questions and their top answers; question references from this endpoint are the starting point for Question Answers. No response was observed for this operation, and the supplied HTTP 200 documentation example is an empty object ({}). Exact JSON field names, nesting, total counts, pagination metadata and behavior for unanswered questions are therefore not verified. Treat community answers as attributed opinions to review, not as confirmed business policies or a complete answer history.

Retrieve a page of answers to a single Yelp community question. The required question input accepts a 22-character question ID obtained from Business Questions or a Yelp question URL. The optional integer page defaults to 1, accepts values from 1 through 1000 and is documented as returning 10 answers per page. Documented response content includes answers, their authors and helpful-vote information. This is a paginated answer listing, not a promise that one request contains every answer. No response was observed for this operation, and the supplied HTTP 200 documentation example is an empty object ({}). Exact JSON field names, author subfields, vote representation, answer ordering, totals and pagination metadata are not verified. Compare community statements with their attribution and available voting context; neither a helpful vote nor an answer implies official business confirmation.

Retrieve discovery context for a known Yelp business: businesses that Yelp recommends alongside it and Yelp collections that feature it, as described in the endpoint documentation. The required business input accepts a Yelp business alias, a 22-character business ID or a Yelp business URL. No page, category, location, radius or ranking controls are documented for this operation. Documented response content has two concepts: recommended businesses and collections featuring the selected business. No response was observed for this operation, and the supplied HTTP 200 documentation example is an empty object ({}), so exact JSON field names, nesting, business attributes, collection metadata, counts and ordering are not verified. Use results as candidates for manual review, not an exhaustive competitor directory, proof of shared ownership or cuisine, or an objective quality ranking.

Retrieve a page of reviews for one Yelp business using its alias, 22-character business ID or Yelp business URL. Combine optional keyword, star-rating and original-language filters; choose from six documented sort orders, or request an additional translation using a two-letter language code. Pagination defaults to page 1 with 20 reviews per page; documented ranges are pages 1–1000 and page sizes 1–49. Saved successful responses contain count, per_page, current_page, total_pages, next, previous, business and reviews. The business object includes id, alias, name, link, rating, review_count, rating_distribution and languages, whose entries contain language and count. Observed review rows include id, link, rating, text, language, translated_text, created_at, date, author, reactions and photos. Author fields include identity, profile link, location, photo link, contribution counts and elite-status fields. Reactions include helpful, thanks, love_this and oh_no. Photo entries include identity, image links, dimensions, upload time, like_count and uploaded_by; caption and tags can be null. Rows also carry is_updated, is_first_review, check_in_count, made_reservation, paid_through_yelp and was_appreciated_by_business. Fields such as videos, owner_reply, previous_reviews, review_of_the_day and expert_badge were null in the observed rows, so their populated structures are not established. A saved newest-sort observation returned three reviews with text, ratings, authors and dates. A separate saved request containing a synthetic keyword returned reviews=[] and count=null, with null navigation values. This observation does not establish why the response was empty; a null count is unknown, not a confirmed zero. translated_text was null in the observed rows. The other sort orders, rating and language filters, and translation behavior are documented capabilities rather than independently verified results. Do not assume complete historical coverage or treat newest ordering as a guaranteed incremental feed.

Request reviews associated with one topic for a specific Yelp business. Supply the business alias, 22-character business ID or Yelp business URL together with a topic name obtained from the Review Topics operation for that business. The documented result contains reviews about the selected topic and a matching snippet, with 20 reviews per page. page defaults to 1 and has a documented range of 1–1000; this endpoint does not expose a page_size input. This operation has no saved response probe, and its supplied response example is an empty object. Topic-matching reviews and supporting snippets are documented response content, not independently observed fields. Exact JSON property names, the snippet layout, pagination metadata, review identifiers and empty-result behavior are not established by the available evidence. Do not infer that it uses the general business-review response schema. Use the snippets to inspect evidence for a returned topic rather than treating a topic label as a complete account of customer experience or as a sentiment score.

Request the phrases reviewers mention most for one Yelp business, identified by its alias, 22-character business ID or Yelp business URL. The documented highlight content consists of a phrase, a supporting snippet, a review count and a photo for each highlight. This operation accepts only business; it has no exposed topic, keyword, rating, sort or pagination controls. There is no saved response probe for this operation, and its supplied response example is an empty object. Phrases, snippets, review counts and photos are documented content rather than independently observed fields. The exact JSON keys, envelope, photo representation, nullability, count calculation and empty-result behavior are not established. Do not assume that a count is the business's total review count or that a photo is always available. Use highlights as pointers for further review reading: mention frequency does not establish positive sentiment, an ordered ranking formula or complete coverage of the review corpus.

Retrieve reviews that Yelp marks as not recommended for a single business. The required business input accepts a Yelp alias, a 22-character business ID or a Yelp business URL. The optional page input defaults to 1 and supports pages 1 through 1000, with a documented page size of 10 reviews. The documented response content is a page of not-recommended reviews with public author statistics. No populated response example or successful response observation is available for this endpoint, so exact review and author field names, total-count fields and empty-page behavior remain unverified. Do not assume every business has results or that pagination provides a complete review history. Preserve the not-recommended designation when storing or comparing results. It is a review-visibility status, not evidence that a review is fake or fraudulent; keep these records separate from the ordinary review sample rather than using them to reconstruct the displayed business rating.

Retrieve the topics discussed in reviews of a single Yelp business, such as food, service or ambience. The required business input accepts a Yelp alias, a 22-character business ID or a Yelp business URL. This operation has no documented topic-filter or pagination input. The documented response content consists of review topics with review counts and sentiment shares. No populated response example or successful response observation is available for this endpoint. Exact JSON field names, sentiment labels, share units, aggregation coverage and empty-result behavior are therefore unverified; do not assume a percentage scale or a particular sentiment breakdown. Use these as reported topic aggregates, not sentiment calculated from a complete local review corpus. When using a topic with the separate reviews-by-topic operation, carry the returned topic value forward rather than constructing a topic identifier or substituting a business-category alias.

Look up Yelp business category names, aliases and parent relationships. All three query inputs are optional: country limits categories to those used in a two-letter country code such as US; parent limits categories to a parent alias such as restaurants; query matches text in category names or aliases, such as pizza. These filters select category definitions, not business listings. An observed successful request with country=US and query=pizza returned an object containing count=1 and a categories array with one entry. Observed entry fields were alias (pizza), title (Pizza), parent_aliases (an array containing restaurants) and countries (null). Treat countries=null as unspecified country metadata, not proof of global support. The single-category result confirms this example relationship, not full taxonomy coverage. The category catalog is documented as containing more than 1,500 categories with parent and supported-country metadata. That total and the shape of non-null countries values were not independently verified. Empty-match behavior, count semantics beyond the observed result and coverage for other country or parent filters remain unverified.

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.

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.

Request location suggestions with the required query string containing a partial place name, such as Beverly Hills. The documented suggestion scope includes cities, neighborhoods and regions. This is a geography suggestion lookup, not a business-name search, business match, address validator or geographic-boundary lookup. No probe response is available for this endpoint, and its provided HTTP 200 source example is an empty object. The documentation describes location suggestions but does not establish exact response keys, list nesting, suggestion types, ranking, identifiers, coordinates, result limits or pagination. Do not assume those fields exist. Use the suggestions to help a person choose a location label before a separate business lookup or geography review. Keep the original query alongside the selected suggestion when traceability matters. No documented guarantee makes a suggestion directly usable as a Yelp Events city slug, and a suggested location does not prove a business exists there.

Get search suggestions for the required query, a partial search term such as piz. The optional location supplies geographic context for tailoring the suggestions. The documented suggestion types are categories, popular search phrases and matching businesses. No nonempty response was independently observed for this operation, and the supplied response example is an empty object, so suggestion property names, grouping keys and business identifier fields are not verified. Treat these suggestion types as documented capabilities rather than a confirmed response schema. Suggestions are not a complete business directory, and popular search suggestions do not establish measured search volume.

Inspect the filter options documented for a Yelp search context. location is required and accepts a city, neighborhood, address or ZIP code; its documented default is Austin, TX. Optionally supply query for a search term and category for a Yelp category alias, category name or Yelp search URL containing cflt=. The documented filter groups cover price, features, categories, distance and service types. This operation has no recorded nonempty response, and its supplied response example is an empty object. Exact response field names, option identifiers, grouping structure and availability of individual filters are therefore unverified. This endpoint describes filter availability; it does not execute a filtered business search. The main business-search operation is not included in this project, and quick search does not accept these filter options.

Find a small set of Yelp business candidates using the required query and location strings. query accepts a business name or keyword, with coffee as its documented default; location accepts a city, neighborhood, address or ZIP code. The optional integer limit has a documented default of 10 and allowed range of 1 to 25. A recorded HTTP 200 request for Golden Boy Pizza in San Francisco, CA with limit=3 returned an object with results containing three business locations, including two San Francisco branches. Observed business records included identifiers, aliases, ratings, phone, website and structured address data. These fields are supported by the recorded observation; the supplied static response example is an empty object and establishes no additional property names, address subfields, pagination fields or availability guarantees. The 1-to-25 range and default of 10 are documented, not independently boundary-tested. Compare branch addresses and phone details before choosing an identifier for a subsequent details, menu or reviews request. This is a candidate lookup, not an exhaustive city directory, a guaranteed exact-name match or a replacement for full business search. It accepts no category, price, distance or service filters.

Retrieve a page of public compliments received by one Yelp contributor. The required user input accepts a 22-character Yelp user ID or a Yelp profile URL. Optional page selects a page from 1 to 1000 and defaults to 1; page_size selects 1 to 50 compliments per page and defaults to 20. The documented response content includes each compliment's type, message, date and sender. These are described attributes, not verified JSON field names: this operation has no observed probe response, and its supplied HTTP 200 example is only an empty object. Response nesting, sender subfields, pagination metadata and empty-result behavior are therefore unverified. Compliments represent community recognition, not verified expertise, business endorsements or contact permission.

Retrieve one public Yelp contributor profile using the required user input, either a 22-character Yelp user ID or a Yelp profile URL. An observed successful HTTP 200 response was a direct user object, not a results list. Observed identity and profile fields were id, name, first_name, link, location, joined, tagline and about; joined was a display string containing a month and year, while tagline and about were null in that response. Integer activity fields were review_count, review_update_count, first_to_review_count, photo_count, video_count, friend_count, follower_count, following_count, question_count, answer_count, events_created_count, expert_recognition_count, compliment_count and reactions_received. The compliments object contained integer counters named thank_you, good_writer, great_photo, just_a_note, cute_pic, hot_stuff, like_your_profile, write_more, you_are_cool, great_lists and you_are_funny. These counters are not individual compliment messages. Elite-related fields included is_elite as a boolean and elite_year, elite_years and is_elite_all_star as null in the observed response. The profile_photos array contained objects with id, link and thumbnail_link strings, plus caption, width, height and uploaded_at, which were null in the inspected photo. The catalog describes biography and Elite-year content, but non-null values and their formats were not established by this sample; the supplied source success example itself was an empty object. Preserve absent or null attributes rather than inventing values. Counts and public profile attributes provide activity context, not verified identity, a trust score, email discovery or permission to contact the person.

Request a page of public Yelp users followed by the selected contributor. The relationship direction is from the selected user to the accounts they follow; this is not a follower list and does not establish mutual friendship. The required user input accepts a 22-character Yelp user ID or a Yelp profile URL. Optional page accepts 1 to 1000 and defaults to 1; page_size accepts 1 to 50 users per page and defaults to 20. The documentation describes followed-user entries with location, Elite status and review counts. These are documented attributes rather than confirmed JSON field names: no probe response was observed for this operation, and the supplied HTTP 200 example is an empty object. The response envelope, identifier keys, Elite representation, total counts, pagination metadata and empty-result behavior remain unverified. Treat any returned relationships as a limited public snapshot, not a complete social graph, a private relationship or permission to contact an account.

Retrieve a page of a Yelp contributor's public friends. The required user parameter accepts a 22-character Yelp user ID or a Yelp profile URL. page accepts 1 through 1000 and has a documented default of 1; page_size accepts 1 through 50 and has a documented default of 20. sort_by accepts newest, oldest, name, name_desc or recently_reviewed, with newest as the documented default. The endpoint documentation describes friend entries with location, Elite status, and review, photo and friend counts. No response was observed for this endpoint, and the supplied success example is an empty object ({}). Those details are documented capabilities, not verified JSON fields: exact keys, the list envelope, pagination metadata and missing-value behavior are unconfirmed. Treat returned pages as a limited snapshot rather than a complete relationship graph. A friends list is not interchangeable with a following list.

Retrieve a page of photos uploaded by one Yelp contributor. The required user parameter accepts a 22-character Yelp user ID or a Yelp profile URL. page accepts 1 through 1000 and has a documented default of 1; page_size accepts 1 through 50 and has a documented default of 20. This endpoint exposes no documented sort, caption-search or business-filter parameter. The endpoint documentation describes each uploaded photo with its caption, date and the business it was taken at. No response was observed for this endpoint, and the supplied success example is an empty object ({}). The caption, date and business association are documented capabilities, not verified JSON fields: exact keys, image URL fields, date format, pagination metadata and missing-value behavior are unconfirmed. Record any missing business association as unresolved. A returned page is not proof of a complete upload history, and access to photo metadata does not grant permission to reuse images or establish that the contributor visited a location.

Retrieve a page of reviews written by a specified Yelp contributor, with optional category, keyword and ordering controls. The required user parameter accepts a 22-character Yelp user ID or a Yelp profile URL. category accepts a Yelp category alias such as pizza, a name such as Coffee & Tea, or a Yelp search URL containing cflt=. query limits the requested reviews to those mentioning the supplied keyword, such as noodles; matching rules are not further specified. sort_by accepts newest, oldest, highest_rated or lowest_rated. Omit it to use Yelp's default ordering, which is not identified as one of those choices in the documentation. page accepts 1 through 1000 with a documented default of 1; page_size accepts 1 through 50 with a documented default of 20. The endpoint documentation describes reviews written by the user together with the business reviewed. No response was observed for this endpoint, and the supplied success example is an empty object ({}). The review-to-business association is a documented capability, not a verified JSON field. Exact review and business keys, whether rating, date or text fields are exposed, pagination metadata and missing-value behavior are unconfirmed. Treat results as a scoped review-history snapshot; do not promise every review, infer physical visits or draw identity or fraud conclusions from the returned material.