App Store reviews,
ready for your code and AI.
Fetch public App Store reviews for any app as structured JSON. Filter by country, language, and platform, then send ratings and review text to your product, research, monitoring, or AI workflow.
TypeScript / JavaScript? Use the open-source SDK: on npm · Source on GitHub
Trusted by developers shipping real products.
2,562,555 served today
Request
$ curl -X POST https://api.fetchlayer.dev/appstore/reviews \ -H "Authorization: Bearer ss-your-key" \ -H "Content-Type: application/json" \ -d '{"appId":"1232780281","country":"us","pages":1}'
Response
{
"reviews": [{
"rating": 1,
"title": "Latest update crashes",
"body": "It closes whenever I open...",
"version": "4.2.0",
"date": "2026-07-28T12:00:00Z"
}],
"pagesFetched": 1
} Built for feedback workflows
Fetch the public signal. Use it wherever your team works.
Public app reviews
Retrieve publicly visible reviews for an App Store app by its numeric app ID—without App Store Connect credentials.
Regional feedback
Narrow review retrieval by country, language, and Apple platform when you need market-specific feedback.
Recent or helpful
Choose recent feedback to monitor what changed, or helpful reviews to surface the most visible customer signal.
Run on your schedule
Call the API from a cron job or automation to keep a feed of new feedback in your own database or alerting workflow.
AI-ready JSON
Pass structured review text, ratings, versions, and dates to an LLM to group bugs, feature requests, and recurring complaints.
Find the app first
Use the App Store search endpoint to resolve an app by name or keyword before fetching its reviews.
Analyze App Store reviews with AI—then export the results to CSV.
Prefer not to write code? Give FetchLayer Research Chat an app, ask what customers love or dislike, and turn the review set into a structured file you can use in a spreadsheet, report, or product workflow.
- ✓Ask questions in plain English
- ✓Analyze themes, sentiment, and pain points
- ✓Download the structured results as CSV or JSON
No code or setup required · Uses your FetchLayer credits
Analyze the recent App Store reviews for this app. Group recurring bugs, feature requests, and praise by theme, then export the reviews and classifications as CSV.
I grouped the reviews into six themes and highlighted the issues most closely tied to the latest app version. The full review-level analysis is ready to download.
app-store-review-analysis.csv
126 reviews · 8 columns · ready to download
Solutions
Build the workflow around the feedback.
Analyze App Store reviews
Turn review text into a cited brief on bugs, feature requests, and customer pain points.
Explore →Monitor new reviews
Build your own recurring review and alerting workflow on top of fresh public feedback.
Explore →Add YouTube comments
Bring another public feedback source into the same data and AI workflow.
Explore →From raw feedback to action
One request is the start of the workflow.
Store the structured response, run it on a schedule, pass it to an LLM, or feed it into the system your team already uses. FetchLayer handles retrieval so you can focus on the outcome.
- 01
Resolve an app
Search the App Store by name or use the numeric app ID from its public listing.
- 02
Fetch the review pages you need
Select country, language, platform, sorting, and pagination controls for the feedback you want.
- 03
Turn feedback into action
Store the JSON, trigger an alert, compare competitors, or ask an AI agent to summarize the recurring themes.
One command.
Your agent does the rest.
Use the App Store endpoint directly from your MCP-compatible agent. Ask it to retrieve public feedback, identify patterns, and turn the result into a useful brief without writing integration glue.
1 Run one command, then sign in
$ npx fetchlayer
◇ Agents
│ Claude Code and Codex
◇ Signed in as you@company.com
◇ Connected
│ ✓ Claude Code ✓ Codex
It opens a sign-in page in your browser. New here? Signing in creates your free account.
2 Ask
›Fetch recent one-star App Store reviews for a competitor and summarize the three most repeated complaints, including the app version each complaint appears in.
fetchlayer.appstore_reviews
Fetched the public review pages and grouped the feedback. The leading issues are crashes after the latest update, slow syncing, and requests for offline access.
No key to copy and nothing to install. New accounts are free, with no credit card.
Use cases
What developers build with App Store review data.
Same API, endless applications. Here is what teams ship with public review data.
Competitor intelligence
Compare public reviews across competing apps to find recurring complaints, unmet requests, and product gaps.
AI agent context
Give Claude, Codex, or your MCP agent structured reviews with app versions and ratings attached.
Review monitoring
Poll recent reviews on a schedule and alert the right team when a complaint cluster begins to grow.
Release intelligence
Track reviews by app version to catch regressions and understand what changed after a rollout.
Product feedback
Turn recurring bugs, requests, and praise into a clean product-research dataset or CSV export.
Market research
Compare public feedback by country and language to understand how customer needs differ across markets.
Compare approaches
Spend time on the insight, not the collection layer.
| What you need | FetchLayer | Official API | Build it yourself |
|---|---|---|---|
| Public competitor review access | ✓ | Owner apps only | You build it |
| Bearer auth from one account | ✓ | Apple setup | You manage it |
| Structured JSON | ✓ | ✓ | You parse it |
| Ready for AI and MCP workflows | ✓ | Your integration | Your integration |
FetchLayer provides access to publicly available data. It is not affiliated with, endorsed by, or sponsored by the platform.
Start free. Scale when ready.
Try it free, buy credits as you go, or take a monthly plan when your volume is steady.
Free
$0
30 requests
Enough to call the platforms you care about and read real responses before you pay anything.
- Every platform and endpoint
- REST and MCP
- No credit card
Pay as you go
$1.99
per 1,000
Buy credits when you need them. They stay on your account until you use them.
- Credits never expire
- No monthly commitment
- Same access as subscribers
- ∞ req/min, ∞ API keys
Monthly plan
Starter$25
per month
15,000 requests a month, about 500 a day.
$1.67 per 1,000, $5 less than credits each month
- ∞ req/min, ∞ API keys
1 page fetched is 1 credit
A normal call reads one page. Ask for more pages and each one is one more credit.
The same on every platform
No multiplier for harder targets, and no charge per result returned.
Nothing back, nothing billed
If a request does not return usable data, it costs 0 credits.
Not sure which volume fits?
15 minutes with the founder. Tell us the workload, we tell you what it needs.
Guaranteed throughput on the platform you run on
A dedicated platform from $400/mo, plus $500 for each ~21 req/s. Every other platform on the same key. 99.95% uptime, 24-hour support on Slack or Telegram.
API reference
Every parameter, documented.
All requests are POST with a JSON body and Bearer auth header.
POST /appstore/search Search the App Store for apps by name or keyword. Returns matching apps with ratings, subtitle, and screenshots.
query* string Search query (app name or keyword) country string Two-letter country code, e.g. 'us', 'gb', 'jp'. Defaults to us. platform string 'iphone' | 'ipad' | 'mac' | 'appletv' | 'watch' | 'realityDevice' geo string Two-letter geo code for regional results POST /appstore/reviews Fetch customer reviews for an app by its App Store ID. Supports filtering by platform, country, language, and pagination.
appId* string App Store app ID (numeric) country string Two-letter country code, e.g. 'us', 'gb', 'jp'. Defaults to us. platforms string[] One or more of 'iphone' | 'ipad' | 'mac' | 'appletv' | 'watch' | 'realityDevice' lang string Language code, e.g. 'en', 'ja' geo string Two-letter geo code for regional results pages number Number of pages to fetch per platform (each platform is paged separately). Billed per page actually retrieved. Default 1. reviewsPerPage number Reviews per page (max 20). Default 20. sort string 'recent' or 'helpful'. Default recent. since string ISO 8601 date (e.g. 2026-01-31). Only returns reviews on or after this date. With sort=recent, pagination also stops once it passes the cutoff — a narrow window can cost far fewer credits than the requested page count. Fields marked * are required. Full API reference →
Guide
How to get App Store reviews through an API.
Short answer: Apple’s own options cover only your apps (App Store Connect API) or stop at 500 reviews per country (the RSS feed). FetchLayer’s App Store Reviews API returns public reviews for any app by ID, filtered by country, language, platform and date, as JSON, at $1.99 per 1,000 requests with 30 free to start, and the same data works over MCP at https://mcp.fetchlayer.dev for Claude, ChatGPT and Cursor. Here is how it works, what the alternatives cost, and the details that trip people up.
1. Find the app ID
Every App Store URL ends in the numeric app ID: apps.apple.com/us/app/notion-notes-tasks-ai/id1232780281 is app 1232780281. If you only have a name, call /appstore/search with it and take the id of the right result.
2. Fetch the reviews
Send the app ID and a country. Each page holds up to 20 reviews; ask for more pages to go further back.
curl -X POST https://api.fetchlayer.dev/appstore/reviews \
-H "Authorization: Bearer ss-your-key" \
-H "Content-Type: application/json" \
-d '{"appId":"1232780281","country":"us","pages":5,"sort":"recent"}'Each review comes back with its id, rating, title, body, author, app version, date and helpfulCount. Use sort: "helpful" for the reviews shoppers see first, and platforms to separate iPhone, iPad and Mac feedback.
3. Only fetch what is new
For monitoring, pass since with the date of your last run. With the default recent sort, the request stops paging as soon as it reaches older reviews, so a daily job usually costs one request per app and country. Store reviews by id and nothing is counted twice.
4. Cover every country you sell in
App Store reviews belong to a storefront, so a US request returns US reviews only. Run the request for each country code and tag each row. Apps with most of their users outside the US often have most of their feedback outside it too.
Your options compared
- App Store Connect API (Apple): reviews for apps you publish, with replies. No competitor data. Needs an App Store Connect API key.
- Customer reviews RSS feed (Apple): any app, but 10 pages of 50, so at most 500 reviews per country, with no language or platform filters. We checked the cutoff on 4 November 2026: page 11 returns an error.
- App intelligence suites (AppFollow, AppTweak, Appfigures): dashboards, with API access on higher tiers. As of November 2026, AppTweak's API plans start at €166 a month, Appfigures lists API access in a $499.99-a-month tier, and AppFollow quotes through sales.
- SERP-style APIs (SerpApi's Apple reviews engine): self-serve from $25 for 1,000 searches a month.
- FetchLayer: any public app, any country, structured JSON, billed per page of up to 20 reviews at $1.99 per 1,000 requests, with 30 free requests to start. The same key covers Google Play reviews and an MCP server for AI agents.
What it costs
One request returns one page of up to 20 reviews. 1,000 reviews cost about 50 requests, roughly $0.10 at pay-as-you-go rates, and monthly plans lower that further (pricing). Failed requests are not billed.
Guides
App Store guides from our blog.
App Store & Play Store MCP Server
Connect FetchLayer's App Store and Google Play MCP tools to Claude Desktop, Cursor, or Claude Code to pull app reviews from any AI agent. Setup and pricing.
Read the guide →App Store Review Sentiment Analysis
Use App Store review sentiment analysis to identify product issues, feature requests, release regressions, and customer pain points from public reviews.
Read the guide →Best App Store Reviews APIs in 2026: 4 Options Compared
Need App Store reviews by API? Apple's App Store Connect API, AppFollow, Apify and FetchLayer compared on competitor access, price and export to CSV or AI.
Read the guide →How to Export App Store Reviews to CSV
Download public App Store reviews to CSV for product research, competitor analysis, monitoring, and AI analysis—with or without code.
Read the guide →How to Scrape App Store Reviews in 2026
Fetch public Apple App Store reviews as structured JSON with a practical API workflow for monitoring, research, and AI analysis.
Read the guide →FAQ
Common questions.
Can I fetch reviews for an app I do not own?
Yes. FetchLayer retrieves publicly available App Store reviews by app ID. You use your FetchLayer API key, not the app owner’s App Store Connect credentials.
What fields are included in an App Store review?
Reviews include the rating, title, body text, author display name, app version, date, helpful count, and a unique review ID where available.
Can I filter reviews by country or language?
Yes. The reviews endpoint supports country, language, platform, sorting, date, and pagination controls so you can retrieve the feedback relevant to your workflow.
Can I fetch only reviews since a certain date?
Yes. Pass a since date (ISO 8601, e.g. 2026-01-31) and only reviews on or after that date are returned. With the default sort=recent, the scraper also stops paginating as soon as it passes the cutoff — so a narrow date window is billed for far fewer pages than the pages parameter alone would suggest. With sort=helpful, Apple's feed isn't date-ordered, so since still filters the results but every requested page is fetched.
Can I use the data with an AI model?
Yes. The API returns structured JSON that you can store, send to an LLM, or access through FetchLayer’s MCP server to find recurring complaints, feature requests, and product feedback.
Can I analyze and export App Store reviews without code?
Yes. FetchLayer Research Chat can retrieve public App Store reviews, analyze recurring themes with AI, and export the structured results as a downloadable CSV or JSON file.
How does billing work?
Review retrieval is billed per page actually fetched: one request per page of up to 20 reviews, shown in pagesFetched. Pay-as-you-go is $1.99 per 1,000 requests, so 1,000 reviews cost about 50 requests (roughly $0.10). The first 30 requests are free, and failed requests are never billed.
Is there an official App Store reviews API?
Apple offers two. The App Store Connect API returns reviews only for apps you publish, behind an App Store Connect API key. The public customer reviews RSS feed covers any app but stops at 10 pages of 50 (500 reviews) per country. FetchLayer returns public reviews for any app by its ID, with country, language, platform, sort and date filters, as JSON.
Can I scrape Apple App Store reviews for a competitor’s app?
Yes. Reviews are public on the App Store, so you can fetch them for any app ID, not just your own. Run the same request for each competitor and country to compare ratings, versions and recurring complaints.
Are App Store reviews different in each country?
Yes. Each App Store storefront has its own reviews, so a US request returns US reviews. Loop over the country codes you care about (us, gb, de, jp…) and tag each review with its country.
Can I get Google Play reviews from the same API?
Yes. The same key works for the Google Play reviews endpoint, which adds rating, keyword, date, app-version and device filters. Many teams pull both stores into one table.
How do I feed App Store reviews into a sentiment or ML pipeline?
Pull reviews on a schedule with since set to the last run, store them by review ID to de-duplicate, then send the title and body to your model. Rating, version and date make useful labels and features. Our sentiment-analysis guide shows the full pipeline.
How do I export App Store reviews to CSV or Google Sheets?
Call the reviews endpoint and write each review’s rating, title, body, version and date as a row. Our export guide has a ready-made script, or Research Chat can produce the CSV with no code.
Start pulling App Store reviews today.
Get a free API key, make your first request, and put public feedback to work in your own product or research workflow.
Used by developers at
Individual developers or teams — not official partnerships