# App Store Storefront Release Propagation and Metadata Parity (`kingii98/app-store-storefront-release-propagation-and-metadata-parity`) Actor

Check version, release notes, price, and minimum OS version for each app in each App Store storefront.

- **URL**: https://apify.com/kingii98/app-store-storefront-release-propagation-and-metadata-parity.md
- **Developed by:** [kingii98](https://apify.com/kingii98) (community)
- **Security:** Limited permissions
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $10.00 / 1,000 actor starts

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 Storefront Release Propagation Ledger

This Actor checks one or more iOS apps in many App Store storefronts. It uses the public Apple lookup endpoint. It needs no key, no login, no proxy, and no browser.

### Who uses it

A mobile release manager uses it after a release. The Actor shows which storefronts show the expected version, release notes, price, and minimum OS version. It also records what changed since the last run.

### Input

| Field | Description | Limit |
| --- | --- | --- |
| `apps` | App Store track IDs or bundle IDs. | 50 |
| `storefronts` | Two-letter country codes. | 60 |
| `expectedVersions` | Optional map from app ID or bundle ID to expected version. | - |

Empty input uses the defaults: app `389801252`, storefronts `us` and `gb`.

### Output

The dataset has two row types.

- `check`: one row for each app and storefront. Fields: `status` (`ok`, `not_found`, `lookup_failed`, `skipped_budget`), `version`, `releaseDate`, `releaseNotesHash`, `price`, `currency`, `minimumOsVersion`, `expectedVersion`, `matchesExpected`, `changedFields`.
- `summary`: one row for each app. It lists `laggingStorefronts`.

A storefront that does not match, is not found, or fails to load counts as lagging when you set an expected version. These results are data. The run still succeeds. A bad input also produces an `input_error` row and a status message. The run still succeeds.

### State

The Actor keeps the last snapshot for each app and storefront in the named key-value store `storefront-release-snapshots`. The first run has no earlier snapshot, so `changedFields` is empty.

### Pricing (pay per event)

| Event | When the Actor charges | Price (USD) |
| --- | --- | --- |
| `actor-start` | One time for each run that starts with valid input. | 0.01 |
| `storefront-check` | One time for each app-storefront check that returns a result from Apple. A not-found check, a failed lookup, and a skipped check are not charged. | 0.002 |

The Actor stops charging when the maximum total charge is reached. It marks the remaining checks `skipped_budget`.

### Safety limits

- The Actor calls only `https://itunes.apple.com/lookup`.
- It does not follow redirects.
- It reads at most 2 MB for each response and waits at most 15 seconds.
- It runs at most 5 requests at the same time.

### Schedule

Use an hourly schedule during a rollout. Use a daily schedule after that.

### Development

```
uv run pytest
uv run ruff check .
```

# Actor input Schema

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

App Store track IDs or bundle IDs. Maximum 50.

## `storefronts` (type: `array`):

Two-letter storefront country codes. Maximum 60.

## `expectedVersions` (type: `object`):

Optional map from app ID or bundle ID to the expected version. Example: {"389801252": "1.0"}.

## Actor input object example

```json
{
  "apps": [
    "389801252"
  ],
  "storefronts": [
    "us",
    "gb"
  ],
  "expectedVersions": {}
}
```

# Actor output Schema

## `results` (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": [
        "389801252"
    ],
    "storefronts": [
        "us",
        "gb"
    ],
    "expectedVersions": {}
};

// Run the Actor and wait for it to finish
const run = await client.actor("kingii98/app-store-storefront-release-propagation-and-metadata-parity").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": ["389801252"],
    "storefronts": [
        "us",
        "gb",
    ],
    "expectedVersions": {},
}

# Run the Actor and wait for it to finish
run = client.actor("kingii98/app-store-storefront-release-propagation-and-metadata-parity").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": [
    "389801252"
  ],
  "storefronts": [
    "us",
    "gb"
  ],
  "expectedVersions": {}
}' |
apify call kingii98/app-store-storefront-release-propagation-and-metadata-parity --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,kingii98/app-store-storefront-release-propagation-and-metadata-parity"
        }
    }
}
```

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/2ogZWVuj7QWb4MCvJ/builds/5h1SPIwErtibG19qh/openapi.json