Skip to content

Apple App Store Listings as Structured JSON

Public App Store pages are a stable surface for app-market research, but collecting them at scale means managing headless browsers, rotating proxies and anti-bot defenses.

OUTPUT FORMATSHTMLJSONMarkdown

This API takes a public apple.com App Store URL, renders the page server-side, and returns either the post-render HTML or parsed JSON. The sections below explain what the endpoint returns, which request fields control rendering and geo, how credits are counted, and where the boundary sits between API concurrency and target-side throttling.

What a single request returns

Each public App Store page exposes the same core surface: app title, developer, version history, screenshots, ratings, review counts, in-app purchase tiers and category position. The endpoint renders that page and returns it to you, so you do not parse raw HTML on your side. You can ask for rendered HTML, or for structured JSON via extraction rules. The same request can also capture a full-page screenshot, or return the page as clean Markdown for downstream LLM analysis. A dashboard request builder generates a ready snippet in Python, Node, Go, PHP, Ruby or cURL, so you can test a URL before wiring it into a pipeline.

Request field and control map

Use this map to pick the field that matches your goal. Each row names the reader goal, the request field that controls it, and what you get back.

From URL to parsed data in four steps

The workflow is deliberately short. Create an account to receive an API key and starter credits. Install an SDK for your stack, or call the endpoint directly. Send the public App Store URL by POST or GET; the service renders the page, handles anti-bot defenses, and returns rendered HTML or structured JSON. When a page needs more, add advanced parameters: render_js for JavaScript execution, stealth_proxy for CAPTCHA-heavy targets, country_code for geo-targeting, and ai_extract_rules for natural-language extraction. Each App Store scrape becomes a single function call, with no proxy rotation or headless Chrome to operate yourself.

Three research workflows this endpoint supports

Review sentiment: pull public App Store reviews and analyze feedback patterns to refine product strategy. Genre and category tracking: capture shifting app categories to spot market gaps, and aggregate apps by category, sub-category and ranking position for app-discovery research or competitor-portfolio tracking. Each of these workflows relies on the same public page surface, so the same request shape works across them.

Worked example: from review pages to a sentiment table

Suppose you want a sentiment table for a set of iOS apps. Start with a list of public App Store URLs. For each URL, send a request with render_js enabled so the page executes its JavaScript, and with extract_rules mapping CSS selectors to field names such as review_text, rating and review_date. The response comes back as parsed JSON, which you can load directly into a sentiment model. If the selectors are unstable, switch to ai_extract_rules with a natural-language spec describing the fields you want. If a target throttles aggressive request patterns, space out requests or use multiple sessions; the API itself applies concurrency limits per plan rather than per-target rate limits.

Concurrency limits versus target throttling

Two different limits can slow a pipeline, and they need different responses. The API enforces concurrency limits per plan, which you resolve by upgrading the plan or reducing parallel requests. The target site may also throttle aggressive request patterns, which you resolve by spacing out requests or using multiple sessions. Treating one as the other leads to wasted upgrades or unnecessary delays.

How credits are counted

API credits are valid for one month and do not roll over. Requests start at one credit each. Enabling JavaScript rendering costs five API credits per successful request. Premium proxies cost ten or twenty-five API credits per successful request, depending on whether JavaScript rendering is disabled or enabled. Geotargeting routes requests through any of 200+ countries and territories, with 40+ available on classic proxies. Screenshots and extraction rules are included on paid plans. These figures describe the cost of successful requests; the source does not state how failed requests are billed, so confirm that with the owner before relying on it in a budget model.

Plan shape at a glance

Standard plans run from Hobby through Business +, and enterprise plans scale further. Every standard plan includes JavaScript rendering, rotating and premium proxies, geotargeting, and screenshots with extraction rules. Priority email support, a dedicated account manager and team management appear from the Business plan upward. Concurrency rises with each tier, from 25 concurrent requests on Hobby to 900 on Enterprise 120. All prices exclude VAT. The full plan table with every credit allowance and concurrency figure is provided as a separate structured module so the exact numbers stay intact.

Data handling and compliance posture

The service does not collect or store personal data from scraped sites unless the user explicitly requests it. Proxy rotation and headless browser rendering are used to reduce IP-based blocking and mimic real user browsing behavior. The platform scales with thousands of headless browsers and rotating proxies, and returns results in roughly one to five seconds across most sites, including JavaScript-heavy ones.

Request field and control map
Reader goalRequest fieldWhat you get back
Execute page JavaScript before capturerender_jsPost-render HTML from a real headless browser
Route through a specific countrycountry_codeResponse from a residential IP in that country
Return structured fieldsextract_rulesParsed JSON keyed by your CSS selectors
Return structured fields without selectorsai_extract_rulesParsed JSON from a natural-language spec
Bypass CAPTCHA-heavy targetsstealth_proxyRendered page with stealth proxy handling
Capture the visual pagescreenshotFull-page screenshot of the rendered page
Return LLM-ready textmarkdownClean Markdown of the page content

Field names are the exact request parameters; the returned shape depends on which field you send.

Frequently asked questions

Can I scrape the Apple App Store without writing code?

Yes. The dashboard request builder lets you paste a URL, set parameters, and copy the generated snippet in Python, Node, Go, PHP, Ruby or cURL. You can test a request before committing to a code path.

How is JavaScript handled on App Store pages?

Send render_js=true. The page runs in a real headless browser, the JavaScript executes server-side, and you receive the post-render HTML.

Can I request App Store data from a specific country?

Yes. Send country_code on the request to route through a residential IP in that country. This is useful when page content varies by geography.

Is there a per-target rate limit?

The API applies concurrency limits per plan, not per-target rate limits. If the target site throttles aggressive request patterns, space out requests or use multiple sessions.

How do I get structured JSON back?

Send extract_rules with CSS selectors mapped to field names, or send ai_extract_rules with a natural-language spec. The response returns as parsed JSON.

Which programming languages are supported?

SDKs are published for Python, Node.js, Go, PHP, Ruby and Java. Plain cURL also works, so you can use whatever your stack already relies on.

How do credits work for a single App Store request?

Requests start at one credit each. Enabling JavaScript rendering costs five API credits per successful request. Premium proxies cost ten or twenty-five API credits per successful request, depending on whether JavaScript rendering is disabled or enabled. Credits are valid for one month and do not roll over.