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.
Short answer: call FetchLayer’s App Store Reviews API with the app’s ID and a country, and write each review as a CSV row. The scripts below export any public app’s reviews from several countries into one Excel-ready file, without duplicates and only from the date you choose. The API costs $1.99 per 1,000 requests, a request returns a page of up to 20 reviews, and the first 30 requests are free. Without code, Research Chat or an AI agent connected over MCP at https://mcp.fetchlayer.dev can produce the same file.
What you get in each row
| Column | What it holds |
|---|---|
id | Apple’s review ID: use it to skip reviews you’ve already exported |
country | The storefront the review came from (each country has its own reviews) |
date | When the review was posted (ISO 8601) |
rating | 1 to 5 stars |
title | The review’s headline |
review | The full review text |
userName | The reviewer’s public display name |
isEdited | Whether the reviewer edited it after posting |
Add your own columns beside these, such as theme, sentiment or urgency from an AI pass, but keep the original text next to them so every classification can be checked.
Find the app ID
It’s the number at the end of the App Store URL: apps.apple.com/us/app/notion-notes-tasks-ai/id1232780281 is 1232780281. Without a URL, look the app up by name with the /appstore/search endpoint.
Export with JavaScript (Node or Bun)
// Export an app's public App Store reviews from several countries to one CSV.
const APP_ID = '1232780281'; // Notion: the number at the end of its App Store URL
const COUNTRIES = ['us', 'gb', 'de'];
const SINCE = '2026-10-01'; // only reviews on or after this date
async function reviews(country) {
const res = await fetch('https://api.fetchlayer.dev/appstore/reviews', {
method: 'POST',
headers: { Authorization: `Bearer ${process.env.FETCHLAYER_API_KEY}`, 'Content-Type': 'application/json' },
body: JSON.stringify({ appId: APP_ID, country, sort: 'recent', since: SINCE, pages: 5 }),
});
if (!res.ok) throw new Error(`${country}: ${(await res.json()).code}`);
const data = await res.json();
return data.reviews.map((r) => ({ ...r, country }));
}
const columns = ['id', 'country', 'date', 'rating', 'title', 'review', 'userName', 'isEdited'];
const cell = (v) => `"${String(v ?? '').replaceAll('"', '""')}"`;
const seen = new Set();
const rows = [];
for (const country of COUNTRIES) {
for (const r of await reviews(country)) {
if (seen.has(r.id)) continue; // never write the same review twice
seen.add(r.id);
rows.push(columns.map((c) => cell(r[c])).join(','));
}
}
// The leading tells Excel the file is UTF-8, so accents and emoji display correctly.
await Bun.write('app-store-reviews.csv', '' + [columns.join(','), ...rows].join('\r\n'));
console.log(`${rows.length} reviews from ${COUNTRIES.join(', ')} written to app-store-reviews.csv`);Run it with bun export.mjs. On Node, use writeFileSync from node:fs in place of Bun.write. On our run (12 November 2026, Notion, three storefronts since 1 October), it wrote 61 reviews.
Export with Python
import csv
import os
import requests
APP_ID = "1232780281" # Notion: the number at the end of its App Store URL
COUNTRIES = ["us", "gb", "de"]
SINCE = "2026-10-01" # only reviews on or after this date
COLUMNS = ["id", "country", "date", "rating", "title", "review", "userName", "isEdited"]
seen = set()
# utf-8-sig writes the byte-order mark Excel needs to show accents and emoji correctly.
with open("app-store-reviews.csv", "w", newline="", encoding="utf-8-sig") as f:
writer = csv.DictWriter(f, fieldnames=COLUMNS, extrasaction="ignore")
writer.writeheader()
for country in COUNTRIES:
res = requests.post(
"https://api.fetchlayer.dev/appstore/reviews",
json={"appId": APP_ID, "country": country, "sort": "recent", "since": SINCE, "pages": 5},
headers={"Authorization": f"Bearer {os.environ['FETCHLAYER_API_KEY']}"},
timeout=120,
)
res.raise_for_status()
for review in res.json()["reviews"]:
if review["id"] in seen: # never write the same review twice
continue
seen.add(review["id"])
writer.writerow({**review, "country": country})
print(len(seen), "reviews written to app-store-reviews.csv")It wrote the same 61 reviews, and Python’s csv module read the file back without errors.
The details that trip people up
- Each country is a separate set of reviews. A US request returns US reviews only, so loop over every storefront you care about and keep a
countrycolumn. - Excel shows accents and emoji as garbage unless the file starts with a UTF-8 byte-order mark. Both scripts write one (
in JavaScript,utf-8-sigin Python). In our export, 36 of the 61 reviews contained characters outside plain ASCII. - Review text contains commas, quotes and line breaks. Quote every cell and double any quotes inside it, as both scripts do, or use a CSV library.
- Re-running an export shouldn’t duplicate rows. Key on
id. For a scheduled export, keep the IDs in a file or database and setsinceto the date of your last run. With the defaultrecentsort, the request stops paging once it passes that date, so a daily export usually costs one request per country. - Apple’s own feeds stop early. Apple’s public customer-reviews RSS feed returns at most 10 pages of 50 (500 reviews) per country, and the App Store Connect API only covers apps you publish.
Open it in Excel or Google Sheets
The file opens directly in Excel, Numbers and LibreOffice. In Google Sheets, use File → Import → Upload and keep the default delimiter. Useful first steps:
- Filter
ratingto 1 and 2 for bugs and churn reasons - Filter
dateto the weeks after a release to see what it changed - Pivot themes against rating, or against country for regional problems
Without code: Research Chat
Research Chat fetches the reviews, classifies them and gives you a CSV or JSON file to download. Start with:
Analyze the recent App Store reviews for this app. Group recurring bugs, feature requests, and praise by theme. Export a CSV with the rating, review text, date, theme, and sentiment.
Then refine the same file: keep only one- and two-star reviews, add an urgency score, split login problems from syncing problems, or rank themes by count.
With your own AI agent
Connect FetchLayer’s MCP server to Claude, Cursor or another client (setup) and ask:
Retrieve App Store reviews for app 1232780281 from the US, UK and Germany since 1 October. Group the complaints by theme, keep each review’s ID and text as evidence, and export the result as CSV.
What it costs
A request returns one page of up to 20 reviews and costs one credit: $1.99 per 1,000 requests pay-as-you-go, less on monthly plans (pricing). 1,000 reviews is about 50 requests, roughly $0.10. Failed requests aren’t billed.
Competitor exports
Reviews are public, so the same scripts work for any app, not just yours. Use one schema for every app and add app_id and app_name columns, so the files can be compared side by side. Public reviewers are self-selecting, so treat the export as evidence about specific problems, not as a survey of every user.
Next steps
- App Store Reviews API: endpoint, filters and pricing
- How to scrape App Store reviews: the full collection guide
- App Store review sentiment analysis
- Export Google Play reviews to CSV
- Connect reviews to Google Sheets, Power BI or Looker Studio: refreshed daily, no CSV step
- Get a FetchLayer API key: 30 free requests, no card