Medium Articles Scraper (tags, authors, publications, claps)

Get the newest Medium stories for any tag, author or publication as flat rows, with claps, responses and reading time attached — no Medium account, no login, no proxy.

What you get

Real rows from the example dataset (tag python):

title	authorName	publication	claps / responses
Computer Vision Meets Generative Art	Lee Vaughan	Data Science Collective	320 / 3
When More Damping Makes Your IK Solver Worse	Luminolous	—	139 / 1
Structuring 40 Million Documents into an Agentic Knowledge Graph	Fareed Khan	Level Up Coding	1057 / 8

Full row: postId, url, title, subtitle, authorName, authorUsername, authorId, publication, publicationSlug, publishedAt, updatedAt, claps, responses, readingTimeMinutes, isMemberOnly, tags, imageUrl, source, sourceKey, rank, scrapedAt.

Use cases

• Newsletter and reading-list curation — the newest stories on your tags, already sorted with claps and responses attached.
• Topic and competitor monitoring — watch a tag or an author and get alerted when something new lands or a story takes off.
• Content research — see which subjects, publications and authors earn claps in a niche before you write.

Try it in 10 seconds

Hit Start/Try it — the input already works: tags: ["python"], tagFeed: latest, maxItems: 20, nothing required. Swap in your own tag, author or publication and run again.

To track a tag or author over time instead of a one-off pull: save the task, set Mode to monitor, and put it on a schedule (Apify → Schedules → cron 0 8 * * * for daily). Each run then returns only stories that are new or whose claps/responses changed since last time.

Related actors

• Substack Scraper (posts, publications, likes, full text) — the same long-form content pattern for Substack publications.
• Reddit Scraper (subreddit posts, search, comments, no login) — see community discussion instead of long-form articles.
• Google News Scraper (search, headlines, alerts, no login) — for headline-level monitoring instead of full articles.

How it works

1. Tags → the tag feed (latest, recommended or archive) is read from Medium's server-rendered page.
2. Users → the author's profile page, newest stories first.
3. Publications → the publication home page, for the stories Medium server-renders there.
4. Rows are flattened and de-duplicated by postId, so the same story reached from two tags is charged once.

Input

Field	Meaning	Default
tags	Medium tag slugs, e.g. python, startup	["python"]
tagFeed	Which tag feed: latest, recommended or archive	latest
users	@usernames or profile URLs	empty
publications	medium.com/<slug> or custom-domain publication URLs	empty
maxItems	Stop after this many story rows	20
mode	scrape or monitor (only new/changed since last run)	scrape
monitorStateId, webhookUrl, telegramBotToken, telegramChatId	Monitor-mode state key and alert targets	empty

Pricing

Event	Price
result	$0.0005 per story ($0.50 per 1,000)
monitor-check	$0.005 per monitor run
change	$0.0005 per new/changed story

Charged only for stories actually pushed. No proxy needed.

Found it useful? A short review on the Store page helps other people find this actor and tells us what to improve. If something is wrong, open an issue on the actor page — issues are answered within a day.

Why this actor

• No login, no cookies and no proxy cost — your bill is the result events plus compute.
• $0.50 per 1,000 stories.
• Engagement is in the row: claps, responses and readingTimeMinutes, not just title and link.
• Monitor mode with webhook and Telegram alerts on new stories and changed clap counts.
• A run that finds nothing pushes nothing and charges no result events; the run summary says why it was empty.

Limits

• Each page returns what Medium server-renders: roughly the newest 10–35 stories per tag or author; publication home pages often render their feed client-side and then return nothing. Run it on a schedule (monitor mode) to accumulate history.
• Story bodies are not included (member-only content stays behind the paywall).

FAQ

Does it need a Medium account or a member subscription? No. There is no login field. Member-only stories appear in the listing with isMemberOnly: true, but their text stays behind the paywall and is never returned.

Can I get the full article text? No. This actor returns story-level metadata only — title, subtitle, author, publication, dates, claps, responses, tags and cover image.

Why did a publication return nothing? Many publication home pages render their feed in the browser rather than on the server, so there is nothing in the HTML to read. Use the tag or the author instead; the RUN_SUMMARY record in the run's key-value store records the reason and no result events are charged.

Changelog

• 0.1, rebuild 2026-09-12 (fix, no schema change): a run whose every page was a block page now ends as blocked in RUN_SUMMARY instead of as an empty dataset with a guessed reason — previously a single-tag run blocked on its first page never reached the three-page threshold.
• 0.1: initial release.

---

If this actor saved you time, a short review on its Store page genuinely helps other people find it. Found a bug or need a field that is missing? Open a ticket on the Issues tab.