Dev.to Articles & Developer Leads Scraper
Pricing
from $0.01 / 1,000 results
Dev.to Articles & Developer Leads Scraper
Scrape Dev.to articles by tag, author, top, or latest and extract developer leads: author name, GitHub, X/Twitter, website, and location. No login or API key. Export to JSON, CSV, or Excel.
Pricing
from $0.01 / 1,000 results
Rating
0.0
(0)
Developer
Mangudäi
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
1
Monthly active users
4 days ago
Last modified
Share
Pull articles from Dev.to (the Forem developer community) and turn them into structured data and developer leads. No login, no cookies, no API key. The scraper reads the public Dev.to API and respects its robots rules and rate limits.
What it does
Give it a tag, an author, a "top" period, or the latest feed. For every article you get the post details plus the author's public profile: name, GitHub, X/Twitter, personal website, and location. That mix works for developer marketing, DevRel research, content analysis, and building lists of developers who write about a topic.
Search modes
- By tag: every article under a tag, for example
python,webdev,rust. - By author: everything published by one username.
- Top: highest-ranked articles over the last day, week, month, or year.
- Latest: the freshest posts across Dev.to.
Input
| Field | Description |
|---|---|
| mode | tag, author, top, or latest |
| tag | Tag to scrape in tag mode |
| username | Author username in author mode |
| topDays | Ranking window in top mode (1, 7, 30, 365) |
| maxItems | Cap on articles returned |
| enrichAuthors | Fetch each author's profile for lead fields |
Output
One row per article:
- Article:
title,url,slug,description,publishedAt,tags,positiveReactions,comments,readingTimeMinutes,coverImage,canonicalUrl,organization - Author lead:
authorName,authorUsername,authorProfileUrl,authorGithub,authorTwitter,authorWebsite,authorLocation,authorSummary,authorJoinedAt
Export to JSON, CSV, or Excel, run on a schedule, or call it from the API.
Notes
Author profiles are cached during a run, so scraping many posts from the same person costs one profile lookup. Only public data is collected.
