Playground Sign in Start free
News and finance · substack.com

How to scrape Substack

Substack (substack.com) is a news and finance site. This guide is built from our own checks of its public pages: what the pages contain, whether our requests get through right now, and the request settings that worked.

Working

18 of 20 of our checks passed in the last 7 days (90%).

Last check 2026-10-13 19:04 UTC · last pass 2026-10-13 19:04 UTC · checked with our own requests, never customer data.

Try it in the Playground

Run the code on this page with your own key: 5,000 free credits for 7 days, no card. Get a free API key →

Extraction recipe

The API returns the rendered HTML of the page. Select the fields you need with extract rules (CSS selectors) or parse the HTML on your side. The recipe below is a set of Scrape API extract rules: we ran it through our API on two real Substack pages with the settings on this page and kept only the fields that came back on both. It is checked again every week, and hidden if it stops working.

Articles

Validated 2026-10-13
FieldTypeExample
titletextWill data centers crash the economy?
descriptiontextThis time let's think about a financial crisis before it happens.
imageURLhttps://substackcdn.com/image/fetch/$s_!Qlx9!,w_1200,h_675,c_fill,f...
urlURLhttps://www.noahpinion.blog/p/will-data-centers-crash-the-economy/c...

Examples from www.noahpinion.blog/p/will-data-centers-crash-the-economy/comments on 2026-10-13, shortened.

Sample output (real, trimmed)

{
    "title": "Will data centers crash the economy?",
    "description": "This time let's think about a financial crisis before it happens.",
    "image": "https://substackcdn.com/image/fetch/$s_!Qlx9!,w_1200,h_675,c_fill,f_jpg,q_auto:good,fl_progressive:steep,g_auto/https%3A%2F%2Fsubstack-post-media.s3.amazonaw...",
    "url": "https://www.noahpinion.blog/p/will-data-centers-crash-the-economy/comments"
}
extract_rules (4 rules)
{
    "title": {
        "selector": "meta[property=\"og:title\"]",
        "type": "attr",
        "attribute": "content"
    },
    "description": {
        "selector": "meta[property=\"og:description\"]",
        "type": "attr",
        "attribute": "content"
    },
    "image": {
        "selector": "meta[property=\"og:image\"]",
        "type": "attr",
        "attribute": "content"
    },
    "url": {
        "selector": "link[rel=\"canonical\"]",
        "type": "attr",
        "attribute": "href"
    }
}

Code

Complete scripts: set the UJEEBU_API_KEY environment variable and run them as they are. Each one sends the settings on this page and the extraction recipe, prints the extracted JSON, and prints the credits the request cost (the Ujb-Credits response header) on stderr. A non-200 answer stops the script with the API's error message.

Articles

Runs the recipe on the two pages it was validated on, one after the other.

substack_detail_sdk.py pip install ujeebu-python==0.1.5
# Scrape Substack articles with the Ujeebu Scrape API.
# Settings and extract rules validated on real pages on 2026-10-13 (Ujeebu site guide).
# Uses the official SDK ujeebu-python 0.1.5: pip install ujeebu-python==0.1.5
# Run: UJEEBU_API_KEY=your_key python3 substack_detail_sdk.py

import json
import os
import sys
import time

import requests
from ujeebu_python import UjeebuClient

API_KEY = os.environ.get("UJEEBU_API_KEY")
URLS = [
    "https://www.noahpinion.blog/p/will-data-centers-crash-the-economy/comments",
    "https://www.noahpinion.blog/p/roundup-88-is-it-time-to-panic-yet/comment/340130164",
]
SETTINGS = {
    "js": True,
}
EXTRACT_RULES = {
    "title": {
        "selector": "meta[property=\"og:title\"]",
        "type": "attr",
        "attribute": "content",
    },
    "description": {
        "selector": "meta[property=\"og:description\"]",
        "type": "attr",
        "attribute": "content",
    },
    "image": {
        "selector": "meta[property=\"og:image\"]",
        "type": "attr",
        "attribute": "content",
    },
    "url": {
        "selector": "link[rel=\"canonical\"]",
        "type": "attr",
        "attribute": "href",
    },
}


def scrape(client, url):
    # with extract_rules, client.scrape sends a JSON POST and the API answers {"result": {...}}
    try:
        response = client.scrape(url, params={**SETTINGS, "extract_rules": EXTRACT_RULES})
    except requests.RequestException as error:
        sys.exit(f"Request failed for {url}: {error}")
    if response.status_code != 200:
        try:
            message = response.json().get("message", response.text)
        except ValueError:
            message = response.text
        sys.exit(f"HTTP {response.status_code} for {url}: {str(message)[:300]}")
    print(f"Ujb-Credits: {response.headers.get('Ujb-Credits')}", file=sys.stderr)
    return response.json()["result"]


if not API_KEY:
    sys.exit("Set the UJEEBU_API_KEY environment variable.")

client = UjeebuClient(api_key=API_KEY)

for i, url in enumerate(URLS):
    if i:
        time.sleep(2)  # be polite: one page at a time
    print(json.dumps(scrape(client, url), indent=2, ensure_ascii=False))

SDK tabs use the official Ujeebu SDKs (ujeebu-python 0.1.5, @ujeebu-org/ujeebu-sdk 0.1.2, github.com/ujeebu/ujeebu-go v0.1.8); there is no PHP SDK, so the PHP tab calls the API with curl. For agents and scripts, the same status and settings are at /scrape/substack.json.

Try it yourself

Run this on Substack with your own key

Get a free API key, set UJEEBU_API_KEY and run any script above as it is. 5,000 free credits for 7 days, no card.

Settings that work today

From our health checks over the last 7 days: the cheapest settings that return the real page most of the time.

Endpoint/scrape
jstrue
Costup to 5 credits a request (only HTTP 200 and 404 are billed)

Collect detail page URLs from listing pages first, then fetch each detail page. Our checks run with JavaScript rendering on (js=true): keep it on. Start with the default (rotating) proxy, the cheapest one that passed most of its attempts in our checks.

Try it in the Playground
ProxyAttemptsPassed
Default (rotating)66

The cheapest proxy that passes most of our checks of this site.

Troubleshooting

The failures our own checks of substack.com ran into over the last 7 days, and what got the page in the same check.

What happenedTimesWhat fixed it
The page did not load in time 2 Nothing we tried in the same check. Retry later, one request at a time.

A failed request is not billed: only HTTP 200 and 404 responses cost credits.

What people build with Substack data

  • Media monitoringTrack the articles published on the topics and companies you follow.More on this use case
  • Content for AI and RAGCollect headlines, dates and summaries as structured input for search and LLM pipelines.More on this use case

Limits and etiquette

  • Public pages only. Pages behind a login, and data shown only to signed-in users, are out of scope.
  • Keep the rate modest: fetch pages one after another or with low concurrency, and cache what you already have.
  • robots.txt of www.astralcodexten.com (read 2026-10-13): public pages allowed for generic crawlers; no crawl delay set.
  • Read Substack's terms of service before you collect data at scale, and do not collect personal data you have no basis to process. This guide is not legal advice.

Questions

Can you scrape Substack with Ujeebu?

Yes. 18 of 20 checks of public Substack pages passed in the last 7 days with the settings on this page.

Which settings work for Substack?

Call /scrape with js=true. On the default (rotating) proxy, 6 of 6 attempts passed in the last 7 days.

How many credits does a Substack request cost?

With these settings a request costs up to 5 credits. Only responses with HTTP 200 or 404 are billed: a blocked or timed-out request is free.

Which fields can I extract from Substack?

With the extraction recipes on this page, validated on real Substack pages through our API: articles: title, description, image, url. Pass the recipe as extract_rules in a POST to /scrape and the API returns those fields as JSON.

Is it allowed to scrape Substack?

Its robots.txt allows generic crawlers on the page types in this guide. Collect public pages only, read Substack's terms of service, keep your request rate modest and do not collect personal data you have no basis to process. This is not legal advice.

How fresh is this page?

The status and settings come from our own health checks of substack.com, which run around the clock. Last check: 2026-10-13 19:04:26 UTC; last pass: 2026-10-13 19:04:26 UTC.