# App Store Privacy, IAP & Version History | Appalize (`appalize/app-store-product-page-intelligence`) Actor

Extract App Store privacy labels, in-app purchase prices, subtitles, version history and rating histograms. Compare snapshots to detect metadata changes.

- **URL**: https://apify.com/appalize/app-store-product-page-intelligence.md
- **Developed by:** [Appalize](https://apify.com/appalize) (community)
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $3.00 / 1,000 product snapshots

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the [API](#api) section below.

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).

# README

## App Store Privacy, IAP & Version History | Appalize

Extract App Store privacy labels, in-app purchase prices, subtitles, version history and rating histograms. Compare snapshots to detect metadata changes.

### Quick start

```json
{
  "apps": [
    "570060128"
  ],
  "countries": [
    "us"
  ],
  "maxItems": 10
}
```

### What it collects

- The app's own subtitle and current metadata.
- Developer-declared privacy groups, purposes and data types, plus privacy-policy URL.
- Public in-app purchase names and display prices, including distinct prices with identical names.
- Public version history and release notes.
- Full numeric rating count and five-star histogram, where Apple exposes them.
- Related apps shown by Apple, when present.
- Reusable snapshots and field-level differences against a supplied baseline.

### Monitor changes

Run once and save each result's `snapshot` object. On the next run, pass those objects in `baselineSnapshots`. Match by numeric `appId` and country. `changeStatus` is `baseline-required`, `changed` or `unchanged`; each change carries before/after values. Only fields present in the baseline are compared. There is no automatic cross-run baseline storage. Use your workflow or data warehouse to pass the previous snapshots when scheduling.

### Data limits

IAP prices are public display strings; billing period, product IDs and subscriber eligibility are not inferred. Apple may show only a subset. Privacy labels are developer declarations, not an independent assessment. `not-observed` does not mean no data collection or no purchases. Version history covers what the current page exposes, not every historical release. Page metadata is requested in English; the country selects the storefront. A changed Apple page structure fails the unit instead of fabricating empty fields.

### Output, automation and cost control

Results are stored in the default dataset; use JSON to preserve nested arrays, or export CSV/Excel through Apify. `RUN-SUMMARY` contains counts and source failures. Each row has source and collection time. `maxItems` caps reports/snapshots, not nested reviews or cohort members. Checkpoints deduplicate resumed work; downstream consumers should also use `recordId` within a run because dataset/checkpoint writes are not atomic.

Use the Apify API, schedules, Make, n8n or MCP integration. No Appalize key, App Store Connect credentials or external LLM key is needed. Only Apple App Store is supported.

**Pricing:** $3 per 1,000 successful app/storefront snapshots, plus $0.00005 per Actor start (one event per GB, minimum one). Platform usage is included. Each result includes all nested data; failed units have no result charge. Use the live Pricing tab and maximum charge setting before running.

Built by [Appalize](https://appalize.com). Report reproducible issues with a run ID and non-sensitive input in the Actor Issues tab.

# Actor input Schema

## `apps` (type: `array`):

Apple numeric IDs, bundle IDs or HTTPS App Store URLs.

## `countries` (type: `array`):

Up to 10 Apple storefronts. One report/snapshot per app and country; benchmark emits one cohort report per country.

## `maxItems` (type: `integer`):

Hard cap across all inputs and countries. A rank check or keyword seed is one result with nested data.

## `baselineSnapshots` (type: `array`):

Paste an array of snapshot objects from a previous run. No automatic baseline storage.

## Actor input object example

```json
{
  "apps": [
    "570060128"
  ],
  "countries": [
    "us"
  ],
  "maxItems": 100,
  "baselineSnapshots": []
}
```

# Actor output Schema

## `results` (type: `string`):

No description

## `summary` (type: `string`):

No description

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "apps": [
        "570060128"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("appalize/app-store-product-page-intelligence").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = { "apps": ["570060128"] }

# Run the Actor and wait for it to finish
run = client.actor("appalize/app-store-product-page-intelligence").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "apps": [
    "570060128"
  ]
}' |
apify call appalize/app-store-product-page-intelligence --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,appalize/app-store-product-page-intelligence"
        }
    }
}
```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/xHAD4eX1n1siZwJdH/builds/cEr1iJUJ6sazEaGyR/openapi.json