Multi-Country App Store Review Export avatar

Multi-Country App Store Review Export

Pricing

$0.50 / 1,000 completed results

Go to Apify Store
Multi-Country App Store Review Export

Multi-Country App Store Review Export

Export a bounded recent window of public Apple App Store reviews across an app/country matrix, with stable IDs, rating/version filters, and explicit page coverage.

Pricing

$0.50 / 1,000 completed results

Rating

0.0

(0)

Developer

JJ Toolworks

JJ Toolworks

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

a day ago

Last modified

Categories

Share

Collect a bounded recent window of public Apple App Store reviews for several apps and storefronts in one run. Outputs preserve country, app version, rating, source timestamps, review IDs, and exact source-feed links.

Example

{
"apps": [{"appId": "284882215", "label": "Facebook public reviews"}],
"countries": ["us", "gb"],
"maxPagesPerPair": 2,
"maxReviewsPerPair": 100,
"maxReviewsTotal": 200,
"ratings": [],
"versions": [],
"knownReviewIds": []
}

appId accepts a numeric ID or an HTTPS Apple app URL. Optional label and clientId preserve your client mapping; repeated app IDs use the first submitted mapping. Country codes identify storefronts, not a reviewer's residence or nationality. App availability varies by storefront.

Use the output

Filter recordType=review for review data. recordId combines app, storefront, and source review ID. Other fields include rating, title, text, version, public authorDisplayName, sourceUpdatedAt, parsed timestamp when possible, sourceUrl, and fetchedAt. Apify provides CSV/JSON dataset export.

Filter recordType=pair_status for app/country coverage. Each attempted page is marked ok, empty, or failed. requestedWindowComplete=true means only the requested bounded pages were successfully processed; historyComplete is always false. Apple can return empty pages and later populated pages, so the Actor does not stop on an empty page. An empty response does not establish app validity or an absence of all reviews.

Use ratings, exact versions, and ISO since to build release or support queues. Filters operate after retrieval and cannot recover older reviews the public feed does not return. To suppress reviews you already exported, supply their complete recordId values in knownReviewIds. This identifies new-to-your-checkpoint reviews; it does not prove a new review was just posted. The SUMMARY key-value-store record contains all pair statuses.

Limits and charging

One event per distinct matching review emitted. Known IDs, duplicate rows, excluded filters, malformed rows, failed-page status, and summary/status rows are unbilled. Review pages are fetched once without automatic retries. Public feed availability and rate limits can change.

Bounds: 10 apps, 10 storefronts, 25 distinct app/country pairs, 10 pages/pair, 500 returned reviews/pair, 5,000 returned reviews/run, 2 MiB per page. Ten pages and 500 reviews are this Actor's ceilings, not an Apple promise of history or availability. Reaching an output limit can stop before the requested page window is complete and is labeled capped.

The public feed is hosted by Apple at itunes.apple.com. It has no documented retention or availability service guarantee. For your own authorized app's supported account workflows, consider Apple's App Store Connect Customer Reviews API; that is a separate integration and is not used by this public-feed Actor.

Price and run controls

The launch price is $0.5 per 1,000 completed units ($0.0005 per event), as defined above. Check the current Pricing tab before running. Status and duplicate rows do not add this custom event. Set a maximum charge appropriate for your batch; a run stops when its event budget is exhausted. RUN-SUMMARY records actual accepted events and execution totals.

Automatic replay of an interrupted run is disabled to prevent duplicate charges. Keep the available output, then start a new run for a new execution. A later run is a new billable execution. Completed dataset rows and individually saved files remain available when a budget stops a run. Combined exports, manifests, and snapshots assembled at the end may be absent after a budget stop or interruption; use a sufficient run budget when you need those aggregate files. The initial release uses documented input limits and public source access; external source changes can require maintenance.