Substack Newsletter Posts Scraper: Posts by Newsletter, Subdomain or Domain

Pull the newest posts of any public Substack newsletter: title, link, author, date and summary, one row per post, each row naming the newsletter it came from. Give newsletters by their Substack subdomain, their own domain or any link on them. No login, no API key, no Substack account.

What you get

{
  "newsletter": "slowboring",
  "newsletterTitle": "Slow Boring",
  "id": "https://www.slowboring.com/p/example-post",
  "title": "Example post title",
  "link": "https://www.slowboring.com/p/example-post",
  "author": "<author name as the feed gives it>",
  "pubDate": "Fri, 23 Oct 2026 10:02:22 GMT",
  "summary": "The post's teaser as the newsletter publishes it."
}

newsletter is the name exactly as you gave it, so rows from several newsletters split cleanly by it.

How to use

{
  "newsletters": ["on.substack.com", "astralcodexten", "www.slowboring.com"],
  "maxPostsPerNewsletter": 20
}

Field	Type	Default	Description
newsletters	string[]		Subdomains (slowboring), <name>.substack.com, own domains (www.slowboring.com) or links
maxPostsPerNewsletter	integer	20	The most posts per newsletter; a Substack feed lists its newest 20

Paywalled newsletters still give titles and summaries through their feed; the full text needs a subscription and is not read.

When a newsletter gives no posts the run's status message names it and says why (no newsletter at the address, a name Substack now sends to a profile page, a feed with no posts), and the OUTPUT record lists them under noPosts.

Pricing

Pay per event. Price per 1,000 events:

Event	Base price	Bronze	Silver	Gold
Result	$1.06	$0.95	$0.85	$0.74

Bronze, Silver and Gold are the discounts Apify gives users of its paid plans. The Pricing tab always shows the current prices.

Buyer

• Content researchers and media analysts following what a set of newsletters publishes.
• Newsletter aggregators building reading lists or digests across dozens of publications.
• Competitive intelligence teams tracking what the newsletters of their market publish each week.
• Marketing teams measuring share of voice across the newsletters their buyers read.
• Developers building read later or discovery apps that need structured post data.

Run it through the API

Python, with the apify-client package:

from apify_client import ApifyClient

client = ApifyClient("<YOUR_APIFY_TOKEN>")
run = client.actor("v0iddo/substack-newsletter-posts").call(run_input={"newsletters": ["on.substack.com", "astralcodexten", "www.slowboring.com"]})
for item in client.dataset(run["defaultDatasetId"]).iterate_items():
    print(item)

JavaScript, with the apify-client package:

import { ApifyClient } from 'apify-client';

const client = new ApifyClient({ token: '<YOUR_APIFY_TOKEN>' });
const run = await client.actor('v0iddo/substack-newsletter-posts').call({"newsletters": ["on.substack.com", "astralcodexten", "www.slowboring.com"]});
const { items } = await client.dataset(run.defaultDatasetId).listItems();
console.log(items);

One HTTP call that waits for the run and returns the rows (for runs that finish within 5 minutes):

curl -X POST "https://api.apify.com/v2/acts/v0iddo~substack-newsletter-posts/run-sync-get-dataset-items?token=<YOUR_APIFY_TOKEN>" \
  -H "Content-Type: application/json" \
  -d '{"newsletters": ["on.substack.com", "astralcodexten", "www.slowboring.com"]}'

Use it from an agent (MCP)

Claude, Cursor, VS Code and other MCP clients can call this actor as a tool through the Apify MCP server. Add it to the client's MCP configuration:

{
  "mcpServers": {
    "apify": {
      "url": "https://mcp.apify.com?tools=v0iddo/substack-newsletter-posts",
      "headers": {
        "Authorization": "Bearer <YOUR_APIFY_TOKEN>"
      }
    }
  }
}

FAQ

Do I need an account, cookies or an API key?

No. The actor reads public data without logging in. You only need an Apify account to start it.

How many results can one run return?

Set Posts per newsletter to the number you need. Large jobs can also be split into several runs or scheduled.

How am I charged?

Pay per event, at the prices on the Pricing tab for your Apify plan (the Pricing section of this page lists them). The platform usage of the run is included in those prices, and your spending limit for a run is always respected.

Why did my run return no results?

The status message and the log of the run say why: usually nothing matched the input, or the source did not answer for a moment. Check the input against the example above and run it again.

Can I run it on a schedule?

Yes. Save your input as a task and add a schedule in the Apify Console (daily, hourly or with a cron expression). Each run gets its own dataset, so you keep a history.

Which formats can I export?

JSON, CSV, Excel, XML, HTML table and RSS from the Output tab or the API. Integrations send the rows to Google Sheets, Slack, Make, Zapier, n8n or a webhook.

Is collecting this data allowed?

The actor collects data that the source publishes openly, without a login. Public data can still be personal data under laws such as the GDPR, and sources have their own terms: make sure your use of the data follows the rules that apply to you.

What happens when the source changes?

An automated test runs the actor every day on the example input and checks the rows, not only that the run finished. When a check fails, the actor is repaired and rebuilt; the build history on this page shows each update.

Something is missing or wrong. Where do I report it?

Open an issue on the Issues tab of this actor with the run link. Requests for a new field are welcome too.

Related actors

• Substack Posts Scraper: Archive, Reactions, Comments
• Medium Scraper: Articles by User, Tag or Publication
• Hacker News Scraper: Stories and Comments by Query
• News Article Extractor: Full Text from Links and RSS

Source

Each newsletter's public RSS feed at https://<host>/feed: <name>.substack.com/feed, or the newsletter's own domain. A newsletter with its own domain answers its Substack address with a redirect to <domain>/feed, which the actor follows; it follows no redirect to anything that is not a feed. Every feed host's robots.txt is read first, including the groups it writes for named crawlers (Substack's own allows /feed), and a request is tried up to 3 times when the connection drops or the site is busy.