Substack Intel API
Substack Intel API reads a publication's public Substack endpoints and returns posts as JSON: id, title, slug, postDate, audience, type, subtitle, url, likeCount, commentCount, wordCount and, in post mode, the full bodyText, or a publication profile with name, description and subscriberCount. It costs $0.001 per row ($1.00 per 1,000), needs no login or key, and runs in the Apify Console, API or MCP.
from $0.001 per post or publication row, $1.00 per 1,000 · Updated Nov 2026, version 0.1.20
Key facts
- Price
- from $0.001 per post or publication row, $1.00 per 1,000
- Pricing model
- Pay per event
- Output
- JSON, CSV, Excel, XML, RSS via Apify datasets
- Access
- Apify Console, REST API, Python and JS clients, MCP tool substack
- Version
- Updated Nov 2026, version 0.1.20
- Usage
- 93.1% successful runs (30 days)
- Actor
subimpact/substack-intel-api
Who it is for
- Newsletter analysts tracking publication output and engagement
- Media researchers mapping a writer's archive by date and topic
- Content teams studying headlines and subtitles that earn likes
- Data teams building a corpus of subscription writing for a model
Use cases
Audit a publication's cadence
Run archive mode with maxItems set to a season's worth of posts and read postDate, wordCount and type per row. Sorting by postDate shows publishing rhythm, and wordCount separates short commentary from long essays. Adding likeCount and commentCount per post lets you see which formats in that cadence actually attract engagement rather than just filling a slot.
Pull full text for a corpus
Once you know the slug from archive mode, switch to post mode with postSlug such as investing-in-gimlet and bodyText arrives with the post. That is the field a RAG index or a fine-tuning set needs, and it comes with title, subtitle and url for citation. Keep the id field as the stable key when you re-run to refresh a post.
Track subscriber count over time
Publication mode returns the profile with subscriberCount, description and name. Run it on a schedule and store the value with the run date: Substack does not publish a history endpoint, so repeated snapshots are the only way to build the trend line. postCount comes back null because public endpoints do not expose it.
Compare publications in a niche
Loop the same two calls over a list of slugs, one publication per run, and collect subscriberCount from publication mode with likeCount and commentCount from archive mode. That gives a ranking of reach against engagement for a niche, which is the pair an advertiser or a sponsorship buyer needs before committing to a placement.
Build a headline dataset
Archive rows carry title and subtitle for every post, plus audience and type. Export them to compare how a publication frames the same topic over a year, or to train a model on the phrasing that precedes a high likeCount. Because archive mode is paginated and capped by maxItems, a large publication can be sampled rather than pulled whole.
Output fields
| Field | Type | Description |
|---|---|---|
id | integer/null | Substack post ID |
title | string/null | Post title |
slug | string/null | Post slug |
postDate | string/null | ISO post date |
audience | string/null | everyone / members / paid |
type | string/null | newsletter / post / podcast |
subtitle | string/null | Post subtitle |
url | string/null | Canonical post URL |
likeCount | integer/null | Number of likes |
commentCount | integer/null | Number of comments |
wordCount | integer/null | Approximate word count of body |
bodyText | string/null | Full post body as plain text (post mode only) |
Show all 18 fields
| Field | Type | Description |
|---|---|---|
publication | string/null | Publication slug |
mode | string/null | archive / post / publication |
name | string/null | Publication display name (publication mode) |
description | string/null | Publication description (publication mode) |
subscriberCount | integer/null | Number of subscribers (publication mode) |
postCount | integer/null | Number of posts (publication mode; null — not available from public pages) |
Sample output
From one of our own test runs on 20 Nov 2026, trimmed. Personal data is redacted.
2 rows, first 3 shown
[
{
"id": 225543401,
"title": "The a16z FDE Fellowship is back",
"slug": "the-a16z-fde-fellowship-is-back",
"postDate": "2026-11-19T17:26:00.354Z",
"audience": "everyone",
"type": "newsletter",
"subtitle": "An eight-week cohort of FDE leaders from SpaceXSI, OpenAI, Harvey, and more",
"url": "https://www.a16z.news/p/the-a16z-fde-fellowship-is-back",
"likeCount": 0,
"commentCount": 0,
"wordCount": 486,
"bodyText": null,
"publication": "a16z",
"mode": "archive"
},
{
"id": 225410903,
"title": "Investing in Linq",
"slug": "investing-in-linq",
"postDate": "2026-11-18T17:05:33.106Z",
"audience": "everyone",
"type": "newsletter",
"subtitle": "a16z leads Linq’s Series B",
"url": "https://www.a16z.news/p/investing-in-linq",
"likeCount": 0,
"commentCount": 1,
"wordCount": 839,
"bodyText": null,
"publication": "a16z",
"mode": "archive"
}
]Input
| Field | Type | Required | Description | Default |
|---|---|---|---|---|
publication | string | Yes | Substack slug (e.g. 'a16z') or custom domain (e.g. 'stratechery.com'). For custom domains, the substack slug is preferred when known. | a16z |
mode | string | No | What to fetch: archive (recent posts list), post (full post by slug), publication (publication profile + stats). | - |
maxItems | integer | No | Max posts to return in archive mode (0 = uncapped, safely limited to 5000). | 10 |
postSlug | string | No | Post slug for post mode (e.g. 'investing-in-gimlet'). | - |
Example input
{
"publication": "a16z",
"mode": "archive"
}Pricing
| Event | What it means | Price | Lowest tier |
|---|---|---|---|
post | Per post, archive row, or publication profile returned. | $0.001 | $0.001 |
actor-start | One charge per run. | $0.00005 | $0.00005 |
$1.00 for 1,000 post or publication row units at the listed price.
Prices from the Apify Store on 20 November 2026. Apify shows the final price before each run.
How it compares with other Apify actors
Price per 1,000 posts at Apify Store list prices. Every row is a live listing on the Store, read on 20 Nov 2026, so a buyer can check each number at the source.
| Actor | Price per 1,000 posts (Free plan) | Higher plans (Gold) | Start fee per run | Platform usage | Users | Rating | Last build |
|---|---|---|---|---|---|---|---|
| Substack Intel API — Posts, Archives & Publication Stats This API | $1.00 | $1.00 | $0.00005 | Included | 2 | No reviews yet | 18 Nov 2026 |
| Substack Scraper — Posts, Comments & Newsletter Data | $1.15 | $0.6 | None | Included | 868 | No reviews yet | 18 Nov 2026 |
| Substack Scraper | All-In-One | $2.50 | $1.99 | None | Included | 307 | No reviews yet | 31 Aug 2026 |
| Substack Posts Scraper 📚 | $4.99 | $4.99 | $0.09 | Paid separately | 294 | 2.6 (3 reviews) | 25 Dec 2025 |
| Substack Scraper: Posts, Comments & Notes | $0.3 | $0.3 | $0.00005 | Included | 154 | No reviews yet | 13 Nov 2026 |
Where Substack Scraper — Posts, Comments & Newsletter Data is stronger
Where Substack Scraper — Posts, Comments & Newsletter Data is stronger
- Comment scraping and topic discovery search as well as archives
- Rich author and publication metadata on every post
- Full archive depth, including newsletters on custom domains
Where this API is stronger
- One row type covers archive rows, full posts and publication profiles
- Post body text comes with the same post event rather than a higher priced content event
- Minimal start event, so a short archive pull stays cheap
Where Substack Scraper | All-In-One is stronger
Where Substack Scraper | All-In-One is stronger
- Keyword search with a choice of result type
- Replies to notes and comments can be collected
- Language and recency filters on posts
Where this API is stronger
- Publication profiles with subscriber counts from the same actor
- One documented row shape with body text and word counts
- Archive, post and publication modes behind a single input set
Where Substack Posts Scraper 📚 is stronger
Where Substack Posts Scraper 📚 is stronger
- Very simple keyword input for a quick search
- Podcast and reaction details per post
- Established listing with its own user base
Where this API is stronger
- Also returns publication profiles including subscriber counts
- Post body text and word count included in the row
- Platform usage is included in the event price
Where Substack Scraper: Posts, Comments & Notes is stronger
Where Substack Scraper: Posts, Comments & Notes is stronger
- Substack Notes, nested comment threads and reactor lists
- Custom domains and author profile pages supported
- Date, audience and post type filters
Where this API is stronger
- One row type across archive, full post and publication profile
- Publication mode returns the subscriber count directly
- Minimal start event on top of the post charge
Substack has several good scrapers, and they differ mainly in what they charge for beside the post: content, comments, notes or reactors. The automation-lab and sourabhbgp actors go deepest on threads and notes, while the easyapi listing stays simple. Ours keeps one row type for archives, full posts and publication profiles, with body text in the same event.
Prices are Apify Store list prices, checked 20 Nov 2026. Platform usage 'Paid separately' means Apify bills compute on top of the event price. Check each listing before you buy.
How to run it
- Set publication to the Substack slug, for example a16z, or a custom domain such as stratechery.com.
- Leave mode at archive to list recent posts, and set maxItems, for example 10, the default, or higher for a longer window.
- Switch mode to publication when you want subscriberCount and the publication profile instead of posts.
- For one post, set mode to post and put its slug, such as investing-in-gimlet, in postSlug.
- Run in the Apify Console and read the rows in the dataset; export as JSON, CSV or Excel.
cURL
curl -X POST "https://api.apify.com/v2/acts/subimpact~substack-intel-api/run-sync-get-dataset-items?token=$APIFY_TOKEN" \
-H "Content-Type: application/json" \
-d '{"publication":"a16z","mode":"archive"}'Python
from apify_client import ApifyClient
client = ApifyClient("<YOUR_APIFY_TOKEN>")
run = client.actor("subimpact/substack-intel-api").call(run_input={"publication":"a16z","mode":"archive"})
for item in client.dataset(run["default_dataset_id"]).iterate_items():
print(item)JavaScript
import { ApifyClient } from 'apify-client';
const client = new ApifyClient({ token: '<YOUR_APIFY_TOKEN>' });
const run = await client.actor('subimpact/substack-intel-api').call({"publication":"a16z","mode":"archive"});
const { items } = await client.dataset(run.defaultDatasetId).listItems();
console.log(items);MCP
claude mcp add subimpact-data -e APIFY_TOKEN=<YOUR_APIFY_TOKEN> -- npx -y @subimpact/data-mcp
# Then ask your agent to use the substack tool.n8n
Use the Apify node (Run an Actor).
Actor ID: subimpact/substack-intel-api
Input JSON: paste the example input above.
MCP users: @subimpact/data-mcp exposes these actors as tools, so an agent can call substack directly.
Limits
- postCount is always null, because public Substack endpoints do not expose exact post counts.
- Custom domains may redirect the API paths to their own archives, so the Substack slug is the safer input.
- An uncapped archive run is capped at 5,000 rows.
- Only public posts and profiles are readable; paid or gated content is not returned.
Questions people ask
What does a post or publication row cost?
$0.001 per returned row, which is $1.00 per 1,000 posts, archive rows or publication profiles, plus a $0.00005 charge for starting the run. Platform usage is included in that event price, so there is no separate compute line.
Do I need a Substack account or API key?
No. The Actor calls Substack's public endpoints directly, with no login, no key and no subscription to the publication. Only publicly readable posts and profile data are returned.
Why is postCount null?
Public Substack endpoints do not expose an exact post count, so the field is always null rather than an estimate. Archive mode is how you count posts in practice: it paginates the list, and maxItems caps how many rows a run returns.
How many posts can one archive run return?
maxItems defaults to 10 and takes 0 for an uncapped run, which is safely limited to 5,000 rows. For a very large publication, a high cap is best treated as a sampling decision, since every returned row is a charged event.
Should I use the slug or the custom domain?
Prefer the Substack slug when you know it. A custom domain can redirect the API paths to its own archives, so the response may differ from what the publication returns on Substack itself. The domain form is there for publications whose slug you cannot find.
What is in a post row?
id, title, slug, postDate, audience, type, subtitle, url, likeCount, commentCount, wordCount, publication and mode, plus bodyText when mode is post. Publication rows instead carry name, slug, url, description, subscriberCount and postCount.
Can I monitor a publication weekly?
Yes. Schedule the Actor and keep maxItems small so each run returns only recent posts; new ids are the ones you have not stored. For subscriber growth, add a second scheduled run in publication mode, because the count is only available as a snapshot at the moment you ask.
Need a data source that is not here?
We build and run scrapers for sites that have no public API. Tell us the site, the fields and how often you need them.