Substack's public archive API changes: apex domains now 404 while www. works
A re-test of Substack's public archive endpoints, run two months after an earlier write-up, found several changes. Custom-domain apex URLs such as bigtechnology.com now return a 404 with no redirect, while the www. variant serves the archive, which caused a scraper to silently return zero rows. The archive also moved from offset paging to keyset cursor paging, and the comments token parameter is no longer required. Some fields changed unexpectedly, including truncated_body_text on paywalled posts and a wordcount value that dropped even though the article body stayed identical. The author has updated the scraper to retry with the www. variant and added a dated correction to the original post.
This is an AI-generated summary. ShortSingh links to the original source for the complete article.

Discussion (0)
Log in to join the discussion and vote.
Log in