One-time export vs watchlist lookup

A one-shot run discovers or snapshots public Apple Podcasts metadata and you export the default dataset. A watchlist run re-resolves shows you already know by collection ID. Apple Podcasts Scraper supports both: searchTerm or chartRequests for the first pass, then lookupIds through the official iTunes Lookup API for recurring checks. Official Apple/iTunes endpoints. No proxy is required. It is not affiliated with or endorsed by Apple.

Open Apple Podcasts Scraper on Apify

One-shot export versus recurring lookup versus rank movement

Use this page when the job is choosing a run shape on Apple Podcasts Scraper. Use Apple Podcasts Chart Scraper when the job is storefront Top Podcasts movement, not a collection-ID refresh. Use Apple Podcasts Reviews Scraper when you already have IDs and need public ratings.

One-time export Watchlist (lookupIds) Chart Scraper monitor
Intent Discover or snapshot, then export Re-resolve known collection IDs Emit rank movement when positions change
Primary input searchTerm or chartRequests lookupIds countries, monitorKey, generateMovementReport
You need Apple IDs first? No Yes No — storefront ranks, not a watchlist of shows
Movement between runs No — snapshot only No — metadata refresh Yes — one movement report row when ranks move

When a one-time export is enough

Use a single run when you do not yet have Apple collection IDs, or when a snapshot is the deliverable:

At least one of searchTerm, chartRequests, or lookupIds is required. Start with delivery set to dataset. After the run finishes, open the default dataset and export it (JSON or CSV from the dataset view). Keep the first run small, then raise limit after the output is useful. Leave includeEpisodes false unless recent episode titles materially help; that path is slower.

{
  "searchTerm": "founder podcast",
  "country": "us",
  "limit": 10,
  "includeEpisodes": false,
  "delivery": "dataset"
}

Documented search fields include collectionId, showName, publisher, country, sourceUrl, and fetchedAt. Sample rowType is podcast_search_result. rank is null on search rows; rank belongs to chart requests. See search discovery, chart snapshots, and dataset fields.

When a watchlist of lookupIds is the better lane

A watchlist refresh re-resolves shows you already know. Pass Apple Podcasts collection IDs as lookupIds. Lookup uses the official iTunes Lookup API. Recurring refreshes re-check show metadata without running a new keyword search or chart request.

Get IDs from a prior search or chart export, or from an Apple Podcasts URL (id1535144780 → 1535144780). country applies to lookup requests (default us).

{
  "lookupIds": ["1535144780"],
  "country": "us",
  "includeEpisodes": false
}

Documented lookup fields include collectionId, showName, publisher, country, sourceUrl, and fetchedAt. episodeTitle is present when recent episodes are included. Collection IDs are stable identifiers for recurring checks.

Empty or no-change watchlist polls are described as avoiding payable default-dataset writes when nothing is saved. Use dryRun to validate a setup without saving results or sending webhooks. After the payload is approved, you can set delivery to webhook and provide webhookUrl (Slack, Discord, Zapier, or any HTTP endpoint). See watchlist refresh.

What does not change between the two

A practical split

You have Start with
A topic, and you need matching shows once One-time searchTerm, then export the dataset
A market, and you need who is ranking on this run One-time chartRequests, then export the dataset
Apple collection IDs, and you need a recurring refresh lookupIds watchlist
A new watch or webhook you have not tested dryRun true, then a live watchlist poll
Storefront ranks, and you need new/changed/dropped positions Apple Podcasts Chart Scraper movement monitor

A common sequence is search or charts first, keep the collectionId values you care about, then switch later runs to lookupIds. That is how the outreach shortlist workflow is described. For chart time series you join yourself, keep each snapshot; see chart tracking over time.

Run a search or watchlist refresh on Apify

When is a one-time Apple Podcasts export enough?

Use a single run when you do not yet have Apple collection IDs, or when a snapshot is the deliverable: keyword discovery with searchTerm, a chart snapshot with chartRequests (feedType podcasts or podcast-episodes), or a shortlist you will review once. Keep the first run small and leave includeEpisodes false unless recent episode titles help.

When should I switch to a lookupIds watchlist?

A watchlist refresh re-resolves shows you already know. Pass Apple Podcasts collection IDs as lookupIds through the official iTunes Lookup API. Get IDs from a prior search or chart export, or from an Apple Podcasts URL (id1535144780 → 1535144780). Recurring refreshes re-check show metadata without a new keyword search or chart request.

Does a watchlist compute rank movement?

No. Apple Podcasts Scraper does not compute rank movement, score outreach fit, or invent audience size. lookupIds refresh show metadata. For a source-linked movement report when a saved monitor sees new, changed, or dropped Top Podcasts positions, use Apple Podcasts Chart Scraper.

How do empty watchlist polls bill?

Empty or no-change watchlist polls are described as avoiding payable default-dataset writes when nothing is saved. Use dryRun to validate a setup without saving results or sending webhooks. Billing is pay-per-event: Actor start plus one result event per default-dataset item.

How is this different from Chart Scraper’s monitor?

A lookupIds watchlist re-resolves known collection IDs. Chart Scraper’s monitorKey path emits at most one podcast_chart_movement_report when storefront ranks are new, changed, or dropped. Use the scraper watchlist for show metadata you already track; use Chart Scraper when the job is rank movement on Top Podcasts charts.

How to run it

  1. Open Apple Podcasts Scraper, then the Actor on the Apify Store.
  2. For a one-shot export: set searchTerm or chartRequests, leave delivery on dataset, and export JSON or CSV from the dataset view.
  3. Keep collectionId values you want to monitor. On later runs, pass those IDs as lookupIds.
  4. For a new watch, set dryRun true first. Then run live. Switch delivery to webhook only after the payload shape is approved.

The published Store price is $0.005 per Actor start and $10.00 per 1,000 dataset results ($0.01 per row).

From $10 per 1,000 results

Open Apple Podcasts Scraper on Apify

Related pages

Public Apple and RSS endpoints only. No account session. Not affiliated with or endorsed by Apple.