Medium Scraper: Articles by User, Tag or Publication

Medium RSS Tracker: Posts by User, Tag, or Publication

Pull Medium articles via the public RSS feed for any user, tag, or publication. One row per article: title, link, author, pubDate, summary, categories. No authentication required.

Example output row

{
  "id": "https://medium.com/p/abc123",
  "title": "How I Built a Faster Python Parser",
  "link": "https://medium.com/@alice/how-i-built-abc123",
  "author": "Alice Chen",
  "pubDate": "Fri, 06 Jun 2026 09:14:00 GMT",
  "summary": "A deep dive into tokeniser design…",
  "categories": ["Python", "Programming", "Software Engineering"]
}

How to use

Provide a list of Medium feed paths. Each path maps to a feed type:

Path format	Feed type
@username	User's personal feed
tag/topic-slug	Tag feed (e.g. tag/machine-learning)
publication-slug	Publication feed (the slug in medium.com/

Input schema

{
  "feeds": [
    "@medium",
    "tag/programming",
    "tag/data-science"
  ],
  "maxArticlesPerFeed": 30
}

Field	Type	Default	Description
feeds	string[]	["@medium", "tag/programming", "tag/data-science"]	Medium feed paths to scrape
maxArticlesPerFeed	integer	30	Maximum articles returned per feed

Pricing

Pay per event. Price per 1,000 events:

Event	Base price	Bronze	Silver	Gold
Medium article extracted	$0.20	$0.18	$0.16	$0.14

Bronze, Silver and Gold are the discounts Apify gives users of its paid plans. The Pricing tab always shows the current prices.

Billing is pay-per-result: you pay only for articles actually extracted and pushed to the dataset.

Buyer

• Content marketers tracking competitor publications or trending tags.
• Data scientists building training corpora from Medium posts by topic.
• Growth teams monitoring industry influencer output (@user feeds).
• SEO analysts tracking publish velocity for any Medium publication.
• Newsletter curators pulling fresh articles for a given tag weekly.

Run it through the API

Python, with the apify-client package:

from apify_client import ApifyClient

client = ApifyClient("<YOUR_APIFY_TOKEN>")
run = client.actor("v0iddo/medium-rss-tracker").call(run_input={"feeds": ["@medium", "tag/programming", "tag/data-science"], "maxArticlesPerFeed": 20})
for item in client.dataset(run["defaultDatasetId"]).iterate_items():
    print(item)

JavaScript, with the apify-client package:

import { ApifyClient } from 'apify-client';

const client = new ApifyClient({ token: '<YOUR_APIFY_TOKEN>' });
const run = await client.actor('v0iddo/medium-rss-tracker').call({"feeds": ["@medium", "tag/programming", "tag/data-science"], "maxArticlesPerFeed": 20});
const { items } = await client.dataset(run.defaultDatasetId).listItems();
console.log(items);

One HTTP call that waits for the run and returns the rows (for runs that finish within 5 minutes):

curl -X POST "https://api.apify.com/v2/acts/v0iddo~medium-rss-tracker/run-sync-get-dataset-items?token=<YOUR_APIFY_TOKEN>" \
  -H "Content-Type: application/json" \
  -d '{"feeds": ["@medium", "tag/programming", "tag/data-science"], "maxArticlesPerFeed": 20}'

Use it from an agent (MCP)

Claude, Cursor, VS Code and other MCP clients can call this actor as a tool through the Apify MCP server. Add it to the client's MCP configuration:

{
  "mcpServers": {
    "apify": {
      "url": "https://mcp.apify.com?tools=v0iddo/medium-rss-tracker",
      "headers": {
        "Authorization": "Bearer <YOUR_APIFY_TOKEN>"
      }
    }
  }
}

FAQ

Do I need an account, cookies or an API key?

No. The actor reads public data without logging in. You only need an Apify account to start it.

How many results can one run return?

Set maxArticlesPerFeed to the number you need. Large jobs can also be split into several runs or scheduled.

How am I charged?

Pay per event, at the prices on the Pricing tab for your Apify plan (the Pricing section of this page lists them). The platform usage of the run is included in those prices, and your spending limit for a run is always respected.

Why did my run return no results?

The status message and the log of the run say why: usually nothing matched the input, or the source did not answer for a moment. Check the input against the example above and run it again.

Can I run it on a schedule?

Yes. Save your input as a task and add a schedule in the Apify Console (daily, hourly or with a cron expression). Each run gets its own dataset, so you keep a history.

Which formats can I export?

JSON, CSV, Excel, XML, HTML table and RSS from the Output tab or the API. Integrations send the rows to Google Sheets, Slack, Make, Zapier, n8n or a webhook.

Is collecting this data allowed?

The actor collects data that the source publishes openly, without a login. Public data can still be personal data under laws such as the GDPR, and sources have their own terms: make sure your use of the data follows the rules that apply to you.

What happens when the source changes?

An automated test runs the actor every day on the example input and checks the rows, not only that the run finished. When a check fails, the actor is repaired and rebuilt; the build history on this page shows each update.

Something is missing or wrong. Where do I report it?

Open an issue on the Issues tab of this actor with the run link. Requests for a new field are welcome too.

Related actors

• Substack Scraper: Newsletter Posts by Publication
• Substack Posts Scraper: Archive, Reactions, Comments
• Hacker News Scraper: Stories and Comments by Query
• News Article Extractor: Full Text from Links and RSS

Source

Medium exposes a public RSS 2.0 feed at:

https://medium.com/feed/{path}

No API key required. The feed includes <title>, <link>, <guid>, <pubDate>, <description> (HTML teaser; the actor keeps its text), <dc:creator>, and <category> elements.