Substack Publication & Posts Scraper avatar

Substack Publication & Posts Scraper

Pricing

from $0.30 / 1,000 posts

Go to Apify Store
Substack Publication & Posts Scraper

Substack Publication & Posts Scraper

Scrapes any Substack publication's own public JSON archive API — title, author, publish date, paywall status, word count, likes and comments per post, one row per post, with an RSS fallback and optional full article text.

Pricing

from $0.30 / 1,000 posts

Rating

0.0

(0)

Developer

Murat Uzun

Murat Uzun

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

20 hours ago

Last modified

Share

What is Substack Publication & Posts Scraper?

Substack Publication & Posts Scraper is an Apify Actor that reads any Substack publication's own public JSON archive API (<publication>.substack.com/api/v1/archive) — the same endpoint the publication's own archive page calls in your browser — with an RSS-feed fallback for the rare case the API answers something unexpected. Give it a subdomain handle (bariweiss), a full *.substack.com host, or any post/publication URL — including a custom domain a paid Substack has moved to — and it returns one clean row per post: title, author, publish date, paywall status, word count, reactions and comment count, with an option to also pull each post's full article text. No API key, no login, no proxies.

Why use Substack Publication & Posts Scraper?

  • Media analysts and researchers track a newsletter's output — cadence, word count, paywall mix — across any number of publications in one run.
  • Content and competitive intelligence teams pull a competitor's recent post titles, subtitles and engagement (likes, comments) without opening every post.
  • RAG and archival pipelines turn a publication's back catalog into structured rows, with full article text available via includeBody.
  • Newsletter growth teams measure their own publication's free-vs-paid post mix and engagement over time.

How to use Substack Publication & Posts Scraper

  1. Fill Publications with one or more Substack identifiers — a bare handle (bariweiss), a full subdomain (bariweiss.substack.com), or any post/publication URL, including a custom domain a Substack has moved to.
  2. Set Max posts per publication (default 50) — the Actor pages through the publication's own archive API in batches of 50 until it collects this many posts.
  3. Turn on Include full article text to fetch each post's own page and extract its article body into bodyText (one extra request per post — leave it off for a faster, metadata-only run).
  4. Turn on Free posts only to skip anything marked paywalled and keep only posts anyone can read.
  5. Click Start and export the dataset as JSON, CSV, Excel or HTML from the Output tab.

Example input

{
"publications": ["bariweiss"],
"maxPosts": 50,
"includeBody": false,
"freeOnly": false
}

Example output

{
"publication": "bariweiss",
"publicationName": "The Free Press",
"postId": 215282915,
"title": "The Founder Building an Actual Unicorn. Plus . . .",
"subtitle": "The man fixing San Francisco. Remembering 'Band of Brothers.' Suzy Weiss takes on Hunter Biden's meme coin. And more!",
"slug": "the-founder-building-an-actual-unicorn",
"url": "https://www.thefp.com/p/the-founder-building-an-actual-unicorn",
"publishedAt": "2026-09-12T10:01:48.809Z",
"author": "The Free Press",
"isPaywalled": false,
"type": "newsletter",
"description": "In today's Weekend Press: the founder building a unicorn...",
"coverImage": "https://substack-post-media.s3.amazonaws.com/public/images/6ba5f918.jpeg",
"wordCount": 1050,
"likeCount": 68,
"commentCount": 12,
"bodyText": null,
"error": null,
"scrapedAt": "2026-09-13T20:45:27.640Z"
}

Data table

Substack Publication & Posts Scraper extracts up to 19 fields per row:

FieldTypeDescription
publication, publicationNamestringThe identifier scraped and the publication's display name
postId, title, subtitle, slugnumber, stringInternal post id, title, subtitle/dek and URL slug (postId/subtitle are null via the RSS fallback)
url, publishedAt, authorstringCanonical post URL, publish time (ISO 8601 UTC) and byline(s)
isPaywalled, typeboolean, stringWhether the post is subscriber-only, and its type (newsletter, podcast, thread)
description, coverImagestringShort excerpt and the post's cover image, when it has one
wordCount, likeCount, commentCountnumberApproximate word count, total reactions and total comments (likes/comments are null via the RSS fallback)
bodyTextstringFull article text, only populated when includeBody is on
error, scrapedAtstringSet when the publication could not be read (all other fields null), and the scrape timestamp

Input parameters

ParameterTypeDefaultDescription
publicationsarray["bariweiss"]Subdomain handles, *.substack.com hosts or any post/publication URL
maxPostsinteger50Max recent posts to collect per publication (1-1000)
includeBodybooleanfalseFetch each post's page and extract its full article text
freeOnlybooleanfalseSkip posts marked paywalled/subscriber-only
maxConcurrencyinteger3Publications scraped in parallel (1-20)

Pricing

Substack Publication & Posts Scraper uses pay-per-event pricing: $0.001 per result row, plus a negligible actor-start fee. Reading the latest 50 posts from one publication costs about five cents; ten publications at 100 posts each costs about a dollar. Turning on includeBody adds one lightweight request per post but does not change the per-row price. Set Maximum cost per run and the Actor trims the work to what the budget covers instead of overspending.

Substack Publication & Posts Scraper vs. browsing the archive page

Substack's own archive page loads posts a page at a time in a UI built for reading, not exporting, and it has no built-in bulk-export button. This Actor reads the same public JSON the archive page itself calls, and turns any number of publications into one flat, typed row per post — ready to schedule, filter or feed into a content, analytics or RAG pipeline.

Using Substack Publication & Posts Scraper with AI agents and MCP

Substack Publication & Posts Scraper is pay-per-event with limited permissions — the two requirements for an Actor to be callable through the Apify MCP server at mcp.apify.com. An agent passes a publications list and gets structured post rows back, ready to summarise a newsletter's recent output, check whether a new post since a given date was free or paywalled, or pull full article text for a downstream summarisation step.

FAQ

Does this need a Substack account or API key? No. It reads <publication>/api/v1/archive, the same public JSON endpoint a browser loads when you open a publication's own archive page — no login, no key.

What if the publication moved to a custom domain? Give it the custom domain directly (https://www.thefp.com or any post URL on it) and the Actor queries that domain's own archive API. A bariweiss-style handle still works too — Substack's own redirect from bariweiss.substack.com resolves to the custom domain transparently.

When does the RSS fallback kick in, and what's different about it? Only when the archive API itself answers something other than valid JSON (rare). RSS-sourced rows have no numeric postId, subtitle, likeCount or commentCount (RSS does not carry them) and isPaywalled stays null, since RSS gives no reliable paywall signal. The Actor logs when this happens.

Why is bodyText null even though I turned on includeBody? A request to the post's own page failed, or the post is fully paywalled and Substack renders no readable preview text for it.

How accurate is isPaywalled? From the archive API it reflects Substack's own audience field (everyone vs. restricted) and is reliable. It is only null when the RSS fallback was used and the signal is unavailable.

Is this legal to run? Yes. <publication>/api/v1/archive and <publication>/feed are public, unauthenticated endpoints a Substack publication's own pages call client-side for anyone visiting them; no login wall is bypassed.

Part of the webdatatools web-intelligence suite — every Actor is pay-per-event, runs without proxies or a headless browser, and returns one clean row per entity:

Browse the whole suite at webdatatools, or call ten of these Actors straight from Claude, Cursor or Cline with the webdatatools MCP server.

Website & domain intelligence

Content for AI, LLMs and RAG

Search, video and social

Leads, jobs and company data

Developer, app and research data

Support and feedback

Found a publication layout or edge case it should handle better? Open an issue on the Issues tab.