App Store App Search

What this Actor does

Search and look up Apple App Store apps by name, trackId, or bundleId via Apple's official iTunes Search API. Writes one normalized dataset row per app with icons, screenshots, descriptions, ratings, pricing, and developer metadata.

Input example

{
  "mode": "search",
  "term": "instagram",
  "bundleIds": [
    "com"
  ],
  "country": "us",
  "language": "en_us",
  "limit": 25,
  "entity": "software"
}

Input fields

Search Apple's App Store by free-text term, lookup by trackId, lookup by bundleId, or batch-search across many terms. Each app becomes one normalized dataset row.

• mode (string, user input): Operation mode. 'search' is a free-text query; 'lookup-by-id' resolves Apple trackIds; 'lookup-by-bundle' resolves bundle identifiers; 'batch-search' searches every term in 'terms' independently.
• term (string, user input): Single free-text term used by 'search' mode (app name, keyword, or developer name).
• terms (array, user input): List of search terms used by 'batch-search' mode. Each term becomes its own search call.
• ids (array, user input): List of Apple trackIds (numeric) used by 'lookup-by-id' mode. Apple's lookup endpoint accepts comma-separated batches.
• bundleIds (array, user input): List of iOS bundle identifiers (e.g. com.burbn.instagram) used by 'lookup-by-bundle' mode.
• country (string, user input): Apple storefront country code. Defaults to 'us'.
• language (string, user input): Apple language code (e.g. en_us, ja_jp).
• limit (integer, user input): Maximum apps returned per search term (1-200). Apple's API caps at 200.
• entity (string, user input): App entity type. 'software' is iPhone, 'iPadSoftware' is iPad, 'macSoftware' is macOS.

Output dataset

Each successful upstream response is written to the default dataset.

• input: Original input value submitted to the upstream API.
• result: Full upstream API response.

Developer notes

Set APPSTORE_APP_SEARCH_API_KEY as an Apify secret environment variable. The Actor forwards it as X-API-Key to the upstream API. Use apiBaseUrl only for local or staging QA. Production runs default to the deployed API base URL from service.json. For advanced testing, a requests array can call explicit API paths; normal users should use the service-specific fields above.

Run locally

$apify run

Deploy

$apify push