Reviews
RevVue continuously collects reviews from the platforms your venues live on — Google, TripAdvisor, Facebook, Wolt, Foodora, Uber Eats and more — and turns each one into a processed review: matched to a location, scored, sentiment-analyzed, and categorized. The Reviews API exposes the same data the reviews UI is built on.
Processed reviews
processedReviews is the workhorse query. Each review carries:
- Who and where — reviewer name, profile, photos, the
sourceplatform, and the matchedlocationId. - Scores — the platform
ratingplus RevVue’s normalizedoverallscore. - Analysis — a sentiment from
VERY_NEGATIVEtoVERY_POSITIVE, and topic categories (food, service, atmosphere, …) extracted from the text. - Reply state — the
replyitself and areplyStatus:NOT_REPLIED,REPLIED,SKIPPED,IGNORED, orNOT_APPLICABLE(some sources don’t accept replies).
Filtering mirrors the UI: by location, date range, source, rating, sentiment, category, reply status, whether the review contains text (isTextInReview), and free-text keywords (searchKeyWords). Standard pagination and sorting apply, and count comes back alongside the page.
Replying
mutateReplyReviews writes replies — RevVue posts them back to the source platform where the integration supports it, and replyStatus tracks the outcome. The canReply filter on processedReviews selects reviews eligible for (bulk) replying, which is how “answer everything from last week” workflows are built.
For reviews that need real follow-up rather than a public reply — a complaint worth investigating — createTicketFromReview in the Inbox turns the review into a ticket with the full inbox workflow behind it.
Full operation reference: Reviews API.

