Apple Podcasts dataset fields

Apple Podcasts Scraper writes source-linked show, chart, and episode rows. Official Apple/iTunes endpoints. No proxy is required. The default dataset is the billable surface. This page lists the fields published in the Actor README. There is no separate output schema on the Store page.

Open Apple Podcasts Scraper on Apify

Scraper fields versus Chart and Reviews rows

Use this guide for Apple Podcasts Scraper output. Apple Podcasts Chart Scraper and Apple Podcasts Reviews Scraper publish different rowType values and field lists. Do not join them as one schema.

	Apple Podcasts Scraper	Chart Scraper	Reviews Scraper
Sample / default `rowType`	`podcast_search_result` (search sample)	`chart_rank`	`podcast_review`
Identity	`collectionId`	`showId` (legacy alias `collectionId`)	`podcastId`
Distinctive fields	`rank` on charts; `episodeTitle` when included	`rank`, optional movement-report `changes`	`rating`, `title`, `content`, `reviewId`

Key fields

These identifiers and timestamps are the ones most workflows join on:

showName — show title on the row
collectionId — Apple Podcasts collection ID (stable ID for recurring checks)
rank — chart position when the row comes from a chart request; the published search sample sets this to null
sourceUrl — Apple Podcasts page for the show
fetchedAt — fetch timestamp

rank is a snapshot of that chart request, not computed movement between runs. Compare ranks only within the same storefront. Search discovery uses collectionId and sourceUrl; chart tracking uses rank plus fetchedAt.

All documented output fields

The README output-field list is:

rowType
collectionId
showName
publisher
country
rank
episodeTitle
sourceUrl
fetchedAt

Rows also include source URLs, fetch timestamps, warnings when a source is partial, and stable IDs when the workflow supports recurring change detection. episodeTitle is present when recent episodes are included (includeEpisodes). Sample rowType for search is podcast_search_result.

Sample discovery row

This is the README discovery-row example (placeholder show data):

{
  "meta": {
    "actorName": "apple-podcast-scraper",
    "actorTitle": "Apple Podcasts Scraper",
    "bundle": "Podcast Research & Media Planning Pack",
    "fetchedAt": "2026-05-06T00:00:00.000Z",
    "totalRows": 1
  },
  "rows": [
    {
      "actorName": "apple-podcast-scraper",
      "rowType": "podcast_search_result",
      "collectionId": 1535144780,
      "showName": "Example Podcast",
      "publisher": "Example Network",
      "country": "us",
      "rank": null,
      "sourceUrl": "https://podcasts.apple.com/us/podcast/example/id1535144780",
      "fetchedAt": "2026-05-06T00:00:00.000Z"
    }
  ],
  "warnings": []
}

Start with delivery set to dataset so you can review these fields. Switch to webhook delivery only after the payload shape is approved. dryRun true runs without saving results or sending webhooks.

Inspect dataset fields on Apify

What Apple Podcasts Scraper fields are documented?

The README output-field list is rowType, collectionId, showName, publisher, country, rank, episodeTitle, sourceUrl, and fetchedAt. There is no separate output schema on the Store page. Sample rowType for search is podcast_search_result.

Is rank present on search rows?

The published search sample sets rank to null. rank is a snapshot of that chart request, not computed movement between runs. Compare ranks only within the same storefront. Search discovery uses collectionId and sourceUrl; chart tracking uses rank plus fetchedAt.

When is episodeTitle present?

episodeTitle is present when recent episodes are included (includeEpisodes). Leave includeEpisodes false unless you need that field; the path is slower. The published input does not expose a full-catalog dump.

How do I export the default dataset?

Start with delivery set to dataset so you can review these fields. After the run finishes, open the default dataset and export it (JSON or CSV from the dataset view). Switch to webhook delivery only after the payload shape is approved. dryRun true runs without saving results or sending webhooks.

How do Chart Scraper and Reviews Scraper fields differ?

Chart Scraper raw rows use rowType chart_rank with country, rank, showId, showName, artistName, and sourceUrl. Reviews Scraper raw rows use rowType podcast_review with rating, title, content, and an iTunes Customer Reviews RSS sourceUrl. Do not mix those field lists with Apple Podcasts Scraper’s README list.

Is collectionId the same as Chart Scraper’s showId?

Apple Podcasts Scraper documents collectionId. Chart Scraper raw rows use showId (legacy alias collectionId). Reviews Scraper raw rows use podcastId. Do not join those identity fields as one schema without checking each Actor’s field list.

Do webhook payloads use the same field names?

Review the default dataset before switching delivery to webhook. Documented dataset fields include showName, collectionId, rank, sourceUrl, and fetchedAt, plus rowType, publisher, country, and episodeTitle when recent episodes are included.

Are contact emails or audience size documented fields?

No. This Actor does not document contact emails, audience size, or download counts. Use the published README fields only. Rank and search position are not advertising guarantees.

What is rowType used for?

rowType is the row kind for downstream filters. Sample rowType for search is podcast_search_result. Chart Scraper and Reviews Scraper publish different rowType values (chart_rank and podcast_review). Do not mix those field lists with Apple Podcasts Scraper’s README list.

How is a dataset export priced?

Billing is pay-per-event. The live Store card is from $2.50 / 1,000 results. Published events are Actor Start at $0.005 and result at $0.0025 per default-dataset item ($2.50 per 1,000). The default dataset is the billable surface.

How to run it

Open Apple Podcasts Scraper, then the Actor on the Apify Store.
Choose a source lane: searchTerm, chartRequests, or lookupIds.
Keep the first run small. Leave includeEpisodes false unless you need episodeTitle.
Leave delivery on dataset. After the run finishes, open the default dataset and export it (JSON or CSV from the dataset view).

Billing is pay-per-event: Actor start plus one result event per default-dataset item. The published Store price is $0.005 per Actor start and $2.50 per 1,000 dataset results ($0.0025 per row).

From $2.50 per 1,000 results