Catalog

Substack API

Substack data through one normalized API - per-request USD pricing and no subscriptions.

Endpoints1Providers1From · posts$0.439604/1k results · OctopusFull breakdownRead docs
Uptime
100.00%
30d · 10 calls
Requests
10
30d
Response
3.4s
median · 30d
POST

Posts

Most used
/v1/run/substack.postssubstack.posts
Pull posts from any Substack publication by its URL, or pass a single post URL (…/p/slug) to fetch just that one article. Returns title, subtitle, publish date, paywall status, word count, engagement (reactions, comments, restacks), author profile, publication details, the full article body as text, HTML and Markdown, and optional comment threads.
10 /mo
100.00%
3444ms p50
1
price$0.439604/1k resultsup to $0.0444 / request
Octopus

About the Substack API

Open an endpoint for its live route, a copy-paste cURL and a sample response.

Measured performance

What the Substack API actually does

Every call through AnyAPI over the last 30 days, counted here rather than promised.

100.0%
of calls succeeded (10 calls)
Succeeded on first lane 100.0%
Response time (10 calls)
Typical (p50)
3.4s
Half of requests finish within 3.4s
p99 response time
5.3s
p99 response time: 99% of requests finish within 5.3s

FAQ

About the Substack API

The AnyAPI Substack API returns Substack data as normalized JSON across 1 endpoint: posts. You call one endpoint per job with a single key, and AnyAPI returns one normalized schema whichever source serves it. Pricing is in US dollars, $0.44 per 1,000 results, and never more than $0.0444 for a single request, with no subscription and no monthly minimum. Over the last 30 days, 100.0% of Substack calls through AnyAPI succeeded, with a median response time of 3.4 seconds across 10 measured calls.

Pricing is in US dollars, $0.44 per 1,000 results, and never more than $0.0444 for a single request, with no subscription and no monthly minimum. You fund one USD wallet, each call draws it down, and a failed request costs $0.

One endpoint: posts. Every one takes the same authentication and returns the same normalized response shape, so reaching a second Substack endpoint is a change of URL and nothing else.

Over the last 30 days, 100.0% of Substack calls through AnyAPI succeeded, with a median response time of 3.4 seconds across 10 measured calls. These are AnyAPI's own measurements of traffic through the gateway, recomputed continuously, not a published service-level target.