Do these 3 things before closing this tab:
1Clear out junk files and repair common Windows errors2Scan for outdated or missing drivers - takes under a minute3Repair Windows errors before they cause bigger problemsUse the Google Play Developer API’s reviews.list method to retrieve reviews for an app, then send a reply—or update an existing one—with reviews.reply. Both calls require the androidpublisher OAuth scope, and the caller must also have permission to reply to reviews in Play Console.
What you need before making API calls
- The app’s package name and access to its Google Play developer account.
- Authentication with the OAuth scope
https://www.googleapis.com/auth/androidpublisher. - A user account with the relevant review-reply permission. Google identifies
CAN_REPLY_TO_REVIEWS_GLOBALas the developer-level permission for replying to reviews. Permission changes can take up to 48 hours to propagate, so verify access in Play Console before deploying the workflow. See Google’s Users resource.
Use Google’s client libraries where they fit your language and application architecture, or call the documented REST endpoints directly. See the Google Play Developer API overview.
As an Amazon Associate I earn from qualifying purchases.
For collaborators, Google advises adding separate Play Console users and granting only the permissions they need rather than sharing developer-account credentials. See Google Play Console user access guidance.
Free tools Windows power users keep installed
One-click scans. No signup required.
Retrieve reviews for an app
Call reviews.list with the app’s package name. It is an authenticated GET request with no request body. The method returns reviews along with pagination information; do not assume one response contains every review.
#1 Best Overall
GET https://androidpublisher.googleapis.com/androidpublisher/v3/applications/{packageName}/reviewsThe path parameter is packageName. Optional query parameters include token, startIndex, maxResults, and translationLanguage. Follow the pagination data in the response when retrieving further results, and set a translation language when it suits your workflow. The response includes reviews[], tokenPagination, and pageInfo. Consult the reviews.list method reference for the current request and response definitions.
Read the review and check for an existing reply
Each review has a reviewId and a comments[] array. A comment is user-provided or developer-provided, so inspect both before preparing a response.
Rank #2
userCommentcan include the review text, star rating from 1 to 5, reviewer language, timestamps, app version, device details, and additional device metadata.developerCommentrecords a reply’s text and when it was last modified. Its presence lets your workflow detect an existing reply before deciding whether to create or update one.
Use the returned reviewId for the reply request; do not substitute a reviewer name or another field. Google documents the review and comment fields in the Review resource reference.
PC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11Crashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minuteSend or update a reply
Post a JSON body containing replyText to the reply endpoint for the app and review. The same method creates a reply or updates an existing one.
POST https://androidpublisher.googleapis.com/androidpublisher/v3/applications/{packageName}/reviews/{reviewId}:reply
Content-Type: application/json
{
"replyText": "Thanks for reporting this. We’re looking into the issue."
}Keep the reply within the API’s approximately 350-character limit; longer replies are rejected. HTML tags are stripped, so send plain text rather than relying on markup. The response includes the applied replyText and its lastEdited timestamp. See the reviews.reply method reference.
Build a reliable review-reply workflow
- Authenticate and confirm access. Request the
androidpublisherOAuth scope and confirm that the calling user can access the developer account, target app, and review-reply permission. - List reviews for the package. Call
reviews.listwith the package name. Use pagination parameters and response tokens as needed, and choosetranslationLanguageif appropriate. - Inspect each review. Read its user comment and any developer comment. Use the review’s
reviewIdto identify the reply target. - Send the reply. POST
replyTextto the review’s:replyendpoint, keeping the text within the documented approximate limit. - Record the result. Retain the returned
replyTextandlastEditedfields as confirmation of the applied reply.
Quota and access troubleshooting
Google publishes a default quota of 3,000 queries per minute per quota bucket. Reply to Reviews APIs share a bucket with Publishing and Monetization APIs; actual available quota can depend on the account and API configuration. Check current usage in Google Cloud Console and request additional quota from Google if needed. See Google Play Developer API quotas.
Quick Recap
- Permission errors: Verify the caller’s Play Console access and review-reply permission. If permission was just changed, allow up to 48 hours for propagation.
- Missing reviews: Check pagination rather than treating a single list response as complete.
- Reply rejected: Check that the JSON includes
replyText, that the path uses the correct package name andreviewId, and that the reply does not exceed the approximate character limit. - Quota errors: Review usage and the applicable quota bucket in Google Cloud Console; available limits can vary by configuration.
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
