Google Play reviews API for Android apps

Google doesn't publish a general-purpose public API for pulling any app's Play Store reviews — the Play Console gives developers their own app's reviews, but nothing exists for a competitor's app, and nothing outside the console offers structured, queryable review data at all.

Roketfy's Google Play reviews API fills that gap: pass a Play Store product id and it returns paginated user reviews as structured JSON, for any public app on the store.

The product_id is the package identifier Google Play uses internally — for example, com.spotify.music. It's visible in the app's Play Store URL after id=, and it's stable for the lifetime of the app, unlike a display name that might change.

If you only know an app's name, run the search endpoint first — it accepts a search query, a category, or one of Google Play's own charts (top free, top paid, top grossing) and returns matching apps with their product ids.

Unlike a fixed page-count parameter, the reviews endpoint pages with a next_page_token: the first call returns a page of reviews plus a token, and each following call passes that token back to get the next page. Keep following the token until the response stops returning one, which means you've reached the end of the available reviews.

sort_by controls review ordering using Google Play's own numbering, so you can pull the newest reviews on a recurring schedule rather than always starting from the same default order.

Yes. hl sets the interface language and gl sets the country code Google Play uses to localize both the review language and the country-specific version of the store listing — the same app can carry meaningfully different reviews (and even a different price) depending on which country's store you query.

This matters most for apps with a large audience outside their home market: pulling hl=tr, gl=tr alongside hl=en, gl=us can surface a regional bug, a translation complaint, or a payment issue that a single default-locale pull would never show.

Most consumer and subscription apps ship on both stores, and the two review pools rarely tell identical stories — Android's broader device fragmentation tends to surface more device-specific bugs, while iOS reviews skew toward UX and payment friction on Apple's own platform. Pulling both into one pipeline, keyed by the same app across product_id and app_id, lets a single dashboard show the full cross-platform picture rather than two disconnected ones.

It also gives product teams a cleaner signal on whether a bug is platform-specific or affects every user: a complaint that shows up in both Play and App Store reviews within the same release window is a much stronger prioritization signal than one that shows up in only one.

Review text feeds directly into Android ASO the same way it does on iOS: the words users search for and the comparisons they draw against other apps belong in your own keyword research, not just in a support inbox. Pairing that with the app endpoint's rating and metadata lets you track whether a store-listing change actually moved sentiment over the following release cycle.

On the support side, sorting reviews by newest and scanning for recurring crash, login or billing complaints turns the review stream into an early-warning system — often faster than waiting for support tickets to accumulate through official channels.