Scrape app store reviews at scale: why an API wins

To fetch app store reviews at scale, an API is the more maintainable route than scraping store pages, because an API returns structured, filterable and paginated reviews for App Store and Google Play apps and leaves no scraper to maintain. This article explains why scrapers break as volume grows and how to fetch app reviews with the AppTweak API.

The AppTweak API delivers reviews as structured data through three review endpoints. They differ in what they return, which filters they accept and how they are priced.

Key takeaways

Why does scraping app store reviews break at scale?

A scraper reads a store page or feed, extracts the review text and saves it. That works for a small job. It becomes a maintenance problem when the number of apps, markets or refreshes grows, for five reasons:

• Rate limits and blocks. A scraper sends many requests from few addresses, and stores can slow or block that traffic.
• Terms of use. A store’s terms may restrict automated collection of its pages, so read them before you build a pipeline on scraped data.
• Fragile parsing. A scraper depends on page structure. When a store changes a page or feed, extraction fails until someone updates the code.
• Ongoing maintenance. Someone must own the scraper: monitor failures, fix parsers, and manage proxies and storage.
• Different store formats. App Store and Google Play expose different fields, so each store needs its own parsing and a mapping to one shared schema.

What does fetching app store reviews at scale require?

Fetching app store reviews at scale requires six capabilities: structured fields, filters, pagination, one format for both stores, several apps per request, and metered cost.

The AppTweak API provides these through its review endpoints. AppTweak’s App Store API “gives developers and data teams direct access to the industry’s largest app store database: 17 million+ keywords, 6 million apps, and historical data across 100+ countries since 2014,”

What endpoints does the AppTweak API feature to fetch app store reviews?

The AppTweak API has three review endpoints, one for each job: raw review entries, rating aggregates, and the reviews an app store displays. The App Reviews overview in the developer documentation covers all three.

App Reviews Search: raw review entries

App Reviews Search returns individual review entries for an app. You can filter by date range, rating range, a keyword in the review body, and whether the developer replied. You also select the country, language and device.

Each review carries a rating, a title (usually empty on Google Play), a body, a date, an author name and a review ID. App Store reviews add helpfulness votes. A developer reply is included when one exists.

App Reviews Stats: rating aggregates

App Reviews Stats returns, for each day in a date range, the number of reviews, the average rating and the count per star level. It also returns the same figures aggregated over the whole range. It accepts the same date, rating, keyword and reply-status filters as App Reviews Search.

Use Stats to track rating trends over time. It is priced per app and per day, not per review, so check the pricing table before a long date range.

App Reviews Displayed: reviews as the store shows them

App Reviews Displayed returns the reviews as shown on an app’s store page, sorted by most useful, most recent, most positive or most critical. Most critical is available for App Store apps only.

Use App Reviews Displayed when you need the same view a visitor sees, rather than every review an app has received.

What can you do with app store reviews at scale?

App store review data supports five jobs, and each maps to one endpoint or filter:

• Find recurring bugs and requests. Use Search with keyword and rating filters, for example reviews of one to two stars that mention “crash”.
• Track rating trends. Use Stats to follow average rating and star counts per day, before and after a release.
• Monitor competitors across markets. Use Search with several apps and countries. App Store reviews are grouped by country, while Google Play reviews are grouped by device language, so countries that share a language return the same Google Play reviews.
• Compare countries and languages. Pull the same filters for several markets to see which issues are local.
• Feed analysis pipelines. Structured reviews load into a database or notebook without a parsing step.

For what to do once you hold the data, read the guide to app store reviews. If you prefer no code, the App Reviews Manager handles review monitoring in the AppTweak platform.

How do you fetch app store reviews with the AppTweak API?

A first review pull takes five steps:

1. Subscribe to an API plan, then get your API key from the API dashboard. Send it in the `x-apptweak-key` header.
2. Find the app ID: a number on the App Store, a package name on Google Play. See how to find app IDs.
3. Track the app with the Tracked Applications endpoint by sending a POST request to /user/tracked_applications with application_id, country, language and device.
4. Request reviews with the filters you need.
5. Page through the results, deduplicate by review ID, and check the credits charged.

Example request. This call returns the one- and two-star App Store reviews that mention “crash” for one tracked app in the US, posted in October 2026:

GET https://public-api.apptweak.com/api/public/store/apps/reviews/search.json?apps=284910350&country=us&device=iphone&min_rating=1&max_rating=2&term=crash&start_date=2026-10-01&end_date=2026-10-31&limit=100

x-apptweak-key: YOUR_API_KEY

The response lists each review with its rating, title, body, date and author. Add replied=false to keep only the reviews the developer has not answered.

The developer documentation covers authentication and the full parameter lists. Related guide: keyword suggestions through the API.

Track the app before you request its reviews. App Reviews Search returns reviews for tracked apps, because AppTweak fetches reviews daily for apps that are tracked. Creating a tracked app uses no credits. A tracked app is one combination of app ID, country, language and device, so an app tracked in the US in English and Spanish counts as two. Data can take 24 to 48 hours to appear after you start tracking, and the number of apps you can track depends on your API plan.

What are the limits of fetching reviews via API?

An API removes the maintenance problems of scraping, and it has its own constraints:

• Reviews are available for tracked apps, and tracking an app takes one request to the Tracked Applications endpoint. A tracked app is fetched daily from then on, and the number of apps you can track depends on your API plan.
• Each request is capped: Search and Displayed return up to 500 reviews, all three review endpoints take up to 5 apps, and Search and Stats accept a date range of up to one calendar year. Use the offset parameter to page through larger result sets.
• Stores differ: App Store reviews are per country and Google Play reviews are per device language, and some fields exist on one store only, such as helpfulness votes on the App Store and the app version on Google Play.
• A request that takes too long can time out. Narrow the date range or the number of apps. See HTTP errors.

Conclusion

Scraping is a common starting point to fetch app store reviews, and it fits a small, one-off pull. At scale, an API returns structured reviews from both app stores, with filters, pagination and visible credit costs, and no scraper to maintain. Read the AppTweak API documentation to make your first request, or visit the AppTweak App Store API page to get started.

FAQs