Reviews

Listing reviews

gplay reviews list                       # most recent reviews
gplay reviews list --stars 1-2           # only 1- and 2-star
gplay reviews list --stars 1,3,5         # a set
gplay reviews list --limit 20            # cap the count

--stars filters client-side (the API has no server-side rating filter), results auto-paginate until exhausted, and --output json is the {"reviews": [...]} pass-through reflecting the filtered set.

Viewing one review

gplay reviews view REVIEW_ID              # the REVIEW_ID column of `reviews list`

view is the deep read of a single review: a scalar header (author, star rating, date, locale, device, app version, reviewId) followed by the user↔developer conversation — the review body and any developer replies with their dates. --output json is the Review object verbatim; --output markdown renders a record plus the thread as blockquotes.

Because the API only serves the last 7 days, a REVIEW_ID that is unknown or has aged out of the window fails with exit 30 and a message naming the window — a valid id can still become unfetchable.

Replying

gplay reviews reply --review-id REVIEW_ID --reply "Thanks for the feedback!"

Batch replies

For support workflows (or an agent drafting replies for approval), reply takes a TSV stream — one <review-id>\t<reply text> line per reply, - for stdin:

gplay reviews reply --batch replies.tsv
gplay reviews list --stars 1-2 --output json | my-draft-tool | gplay reviews reply --batch -

Blank lines and # comments are skipped; replies containing tabs or newlines use RFC 4180 double-quoting. Each line posts sequentially — a failing line is reported on stderr and does not abort the rest, and the process exits with the highest exit code seen.

Use --dry-run to parse and print the planned replies without calling the API.

Permissions

Replying requires the "Reply to reviews" permission on the service account in the Play Console — gplay auth doctor and the service account setup page cover granting it.