Retrieve a Yelp User's Reviews with Filters
View all Yelp Business, Reviews & Restaurant Data endpoints →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.
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/user-reviews API Response (JSON)
{} curl -X GET 'https://api.opendata-api.com/api/project/yelp/user-reviews?key=<API_KEY>&user=CHV3OXUzMbMDZ5A07UGO5A'
Query Result
Use Cases
- Prepare a contributor-requested review-history snapshot that records category, keyword, ordering and page selections, explicitly marking missing pages rather than claiming a complete account export.
- Build a pizza-focused review reading list for a known contributor using category=pizza, keeping each returned review associated with its reviewed business where available.
- Find a contributor's reviews mentioning noodles for a user-requested topic review, without assuming undocumented search matching behavior.
- Compare highest_rated and lowest_rated review samples within an approved contributor study, describing the selected ordering without inferring actual visits or fraud.
Frequently asked questions
Which contributor identifiers work for a user-review request?
The required user parameter accepts a 22-character Yelp user ID or a Yelp profile URL. The endpoint requests reviews authored by that contributor, not all reviews of a particular business.
What can I pass in category to filter a user's reviews?
The documentation accepts a Yelp category alias such as pizza or italian, a category name such as Coffee & Tea, or a Yelp search URL containing cflt=. Omit category when you do not want to request that filter.
How does keyword filtering work?
Set query to a keyword, for example noodles, to request reviews mentioning it. The documentation does not establish case sensitivity, stemming or other matching rules, so do not assume those behaviors.
Can I order a user's reviews by date or rating?
sort_by accepts newest, oldest, highest_rated and lowest_rated. Omitting it uses Yelp's default ordering; the documentation does not identify that default as newest or any other listed choice.
Do the pagination settings guarantee a complete review history?
No. page accepts 1 through 1000 with a documented default of 1, and page_size accepts 1 through 50 with a documented default of 20. These bounds do not prove that all reviews or pages are available; record your filters and any missing pages with the snapshot.
Which review response fields have been verified?
None were observed for this endpoint. The documentation describes reviews with the business reviewed, but the supplied success example is only {}. Exact JSON keys, exposed rating, date or text fields, pagination metadata and missing-value behavior remain unconfirmed.