Google Play Reviews API Alternatives

There is no official Google API for reading Google Play reviews of apps you don’t own.

That’s the whole reason this category exists. The Play Developer API covers apps in your own Play Console account — you can read and reply to your own reviews, and that’s it. There is no public, documented endpoint for pulling reviews of a competitor’s app, or for analyzing reviews across a category.

So if your question is “what are users saying about the three apps we compete with,” the official tooling has no answer, and you’re choosing between third-party APIs.

What the official options actually cover

Play Developer API (Reviews): your own apps only, requires Play Console access and a service account, includes reply capability. Genuinely good for what it does — if the app is yours, use it, especially since replying is only possible there.

Its limits for analysis work: reviews are typically available for a limited recent window rather than the app’s full history, and there’s no cross-app querying. It’s an operations API, not a research one.

Play Console UI: manual export, your own apps, awkward to automate against.

Neither covers the competitive case at all.

Alternative 1: Third-party review APIs

FetchLayer

FetchLayer’s Google Play Reviews API takes a package name or Play Store URL and returns filtered, structured reviews:

curl -X POST https://api.fetchlayer.dev/playstore/reviews \
  -H "Authorization: Bearer ss-your-key" \
  -H "Content-Type: application/json" \
  -d '{
    "appIdOrUrl": "com.spotify.music",
    "ratingFilter": [1, 2],
    "recentDays": 30,
    "appVersion": ["8.9.0"],
    "reviewsPerPage": 200,
    "sortBy": "newest"
  }'

Why it’s different:

• Server-side filtering by rating, keyword, app version, device type, language, and date range — you pay for the reviews you want, not everything then filter locally
• appVersion on every review, which makes release-regression detection possible
• reviewsPerPage up to 200 — far fewer requests than APIs capped at 20 per page
• Real ISO timestamps, not relative date strings, so diffing and sorting work properly
• $1.99 per 1,000 requests, free tier, no credit card
• Same key and JSON conventions as the App Store, Google Maps, YouTube, Reddit, and Twitter/X endpoints
• MCP server included for AI agents

Best for: Competitor tracking, release regression monitoring, and teams already pulling App Store reviews who want both stores on one integration.

AppFollow

AppFollow is a full ASO and review-management product rather than a raw API — dashboards, reply workflows, team assignment, and integrations with Slack and Zendesk. It has an API, but you’re buying the platform.

Best for: Support and ASO teams who want a managed product with a UI, not developers building a pipeline.

Appbot

Appbot focuses on review analytics and sentiment classification across app stores, with categorization and trend dashboards built in.

Best for: Teams who want sentiment analysis as a managed feature rather than running their own classification.

Data365

Data365 offers app store data as part of a broader social and app data API.

Best for: Projects already using it for other social data.

Alternative 2: Open-source scrapers

google-play-scraper (Node) and google-play-scraper (Python) are the well-known libraries here. They’re free, widely used, and genuinely work.

import gplay from 'google-play-scraper';

const reviews = await gplay.reviews({
  appId: 'com.spotify.music',
  sort: gplay.sort.NEWEST,
  num: 100,
});

The honest trade-off:

In favor: free, no API key, no vendor, full control, and for a one-off research pull they’re the fastest path to data.

Against: you own the maintenance. These libraries break when Google changes its internal response format, and the fix arrives whenever a volunteer maintainer gets to it. You also supply your own proxies once one IP isn’t enough, and rate limiting tends to surface as truncated results rather than clean errors — your job “succeeds” with a fraction of the data.

For a research script, that’s fine. For something a dashboard depends on, you’ve adopted a dependency whose SLA is “someone’s spare time.”

Best for: One-off analysis, academic research, prototypes.

Alternative 3: Build it yourself

Playwright against the Play Store listing. Everything in the open-source section applies, minus the community maintenance. Rarely the right call now that mature libraries exist.

Best for: Genuinely unusual requirements the libraries don’t cover.

Comparison

Verify current pricing directly with each vendor before committing — rates and packaging in this category change.

Which should you pick?

It’s your own app and you need to reply → Play Developer API. Nothing else can post replies.

You’re tracking competitors → Any third-party option; the official API cannot do this at all.

You want release-regression alerts → FetchLayer or a library, filtering on appVersion. See the scraping guide for a working implementation.

You want a dashboard, not a pipeline → AppFollow or Appbot. Don’t build a UI someone already sells.

It’s a one-off research question → google-play-scraper. Free, and you don’t care if it breaks next month.

You already pull App Store reviews → Whatever covers both stores on one integration, so you’re not maintaining two auth models and two JSON shapes for the same analysis.

Frequently asked questions

Is there an official Google Play API for competitor reviews?

No. The Play Developer API is scoped to apps in your own Play Console account. There is no public, documented Google endpoint for reading reviews of apps you don’t own — which is why every option in this post is third-party.

Can I get reviews for a specific app version?

Yes, and it’s one of the more useful things you can do with Play Store data — each review carries the appVersion it was left against. Filter on it to compare rating distribution before and after a release. The scraping guide includes regression-detection code.

Is scraping Google Play reviews legal?

Public reviews are publicly visible content, and reading them doesn’t involve bypassing authentication. Reviewer display names are personal data under GDPR even when public, so handle or drop that field accordingly if you’re storing history in the EU or UK. Consult your own counsel for your specific use case.

How far back do reviews go?

Depends on the app and the option you use. Public listing pagination reaches a long way for most apps but is not guaranteed exhaustive — treat results as a large sample rather than a complete census, and store what you pull if you need a durable history.

Next steps

• Google Play Reviews API — endpoint and pricing
• How to scrape Google Play reviews — filtering and regression detection
• Export Google Play reviews to CSV — spreadsheet workflow
• Best App Store review APIs — the iOS equivalent