Stack Overflow Profile Scraper — $2.8/1K · Emails & Reputation
Pricing
from $2.80 / 1,000 results
Stack Overflow Profile Scraper — $2.8/1K · Emails & Reputation
Collect public Stack Overflow profile, reputation, tag and bio fields; only explicitly published contacts. Bulk export: JSON, CSV, Excel and API. PPE: $2.8/1K profiles; start fee extra.
Pricing
from $2.80 / 1,000 results
Rating
0.0
(0)
Developer
Apivault Labs
Maintained by CommunityActor stats
0
Bookmarked
3
Total users
1
Monthly active users
a month ago
Last modified
Features
Share
Stack Overflow Profile Scraper — Reputation, Tags & Public Bio
Look up public Stack Overflow developer profiles by URL or user ID. Get exact reputation, separate answer/question counts, badge counts, public bio, website and up to five contribution tags. Use this to enrich a known developer shortlist or compare public contributions in a workflow.
No Stack Exchange key is required. Running through the Apify API requires your Apify token. This Actor uses the official public Stack Exchange API; its data can be cached and its anonymous quota is shared by source IP. It does not guarantee real-time freshness, private email access, verified identities or unlimited throughput.
Quick start
{"profileUrls": ["https://stackoverflow.com/users/22656/jon-skeet","https://stackoverflow.com/users/1144035/gordon-linoff"],"maxProfiles": 100,"maxConcurrency": 3,"timeout": 90}
You can also supply a positive user ID string such as "22656". Profile slugs and tracking parameters are removed before deduplication. Only public stackoverflow.com/users/ID profiles are accepted; Stack Exchange sibling sites, Teams, question/search URLs, private addresses and URLs containing credentials are rejected.
Omitting profileUrls runs the sample profile and can incur the usual result/start charges. An explicit "profileUrls": [] returns an empty Dataset and summary; the start charge still applies. Up to 1,000 input entries are accepted, with at most 100 unique valid profiles collected. maxProfiles applies after canonical deduplication; capped inputs are counted in SUMMARY. Results follow input order.
Field selection and meaning
All selectors default to true. Existing selector names remain compatible with earlier integrations.
| Input selector | Output | Meaning |
|---|---|---|
extractUsername | username | Public display name, not a unique handle. |
extractFullName | fullName | Compatibility alias of that display name; not a verified legal name. |
extractBio | bio, socialLinks | Plain-text public about-me bio and HTTP(S) links in it; links can include books or blogs as well as social profiles. External sites are not fetched. |
extractLocation | location | Publicly provided location; blank when absent. |
extractFollowers | reputation | Exact reputation integer. This legacy selector does not return followers or people reached. |
extractPosts | answerCount, questionCount | Separate source integers; missing counts are null, not invented zeroes. |
extractProfileUrl | profileUrl | Canonical profile URL. Attribution and input URL remain in metadata. |
extractEmail | email | First email explicitly written in public bio text or a mailto link. Blank when absent; no guessing or email verification. |
extractWebsite | website | Public profile website URL. |
extractCategory | specialization | Up to five official top contribution tag names, joined as text. Tags are not verified professional skills. |
extractMetadata | otherMetadata | Badges, member-since/update timestamps, collectives when returned, and top tags with counts and scores. |
otherMetadata.topTagsLimit is 5. topTagsHasMore: true means more tags exist; this Actor intentionally returns only the first five. If optional tag enrichment fails, core profiles can still be delivered, with topTagsHasMore: null and a WARNINGS record. Unknown source fields remain blank or null. There is no full tag history, follower/reach metric, question/answer text, catalog search or developer discovery by skill.
Every paid row must match the requested user ID, contain a public name and valid reputation, and contain useful selected fields. Selecting only a URL, unavailable email, or disabling every field produces NO_SELECTED_DATA and no paid profile row.
Output
Illustrative subset; names and counts change over time:
{"success": true,"userId": 22656,"inputUrl": "https://stackoverflow.com/users/22656","username": "Jon Skeet","fullName": "Jon Skeet","reputation": 1530000,"answerCount": 35805,"questionCount": 56,"website": "http://csharpindepth.com","specialization": "c#, java, .net, linq, string","profileUrl": "https://stackoverflow.com/users/22656","source": "Stack Exchange API","attributionUrl": "https://stackoverflow.com/users/22656","identityValidated": true,"freshnessVerified": false,"fullNameVerified": false,"observedAt": "2026-10-11T20:00:00+00:00"}
Only selected profile fields are returned, plus collection/identity/attribution metadata. observedAt is collection time, not the source's last update. identityValidated means the public profile ID matched; it does not verify a person's real-world identity. Use profile attribution links when redistributing bio content and follow the source's applicable content license.
Results, errors and retries
- Dataset: useful profile rows only, exportable as JSON/CSV/Excel.
- SUMMARY: requested, uniqueRequested, delivered, failed, duplicates, capped, warnings, apiRequests, quotaRemaining and status.
- ERRORS: rejected input, missing profile, invalid response or source access/quota errors. Invalid URLs are not echoed; errors are not paid Dataset rows.
- WARNINGS: optional top-tags failures with affected user ID and safe retry advice.
- RETRY_INPUT: canonical URLs for retryable profile or enrichment failures. A retry can charge again for a newly delivered profile; inspect existing results first.
All failed profiles cause a FAILED run with no profile-result events. Mixed successes/errors or core profiles with enrichment warnings are SUCCEEDED with SUMMARY.status: "partial". An explicit empty list is SUCCEEDED with zero results. Read the counts and reports; run status alone does not prove complete data.
The official API can return quota exhaustion, rate limiting or backoff. The Actor batches core profile lookup, spaces requests and honors source backoff; it does not rotate proxies to bypass quota. Optional tag workers are bounded by maxConcurrency (1–20), while actual API requests are serialized. Source failure is reported rather than converted to an empty successful profile. No private upstream diagnostics or credentials are exposed.
API and n8n
curl -X POST \'https://api.apify.com/v2/acts/I2ZH6abZW68mjgh01/runs' \-H 'Authorization: Bearer YOUR_APIFY_TOKEN' \-H 'Content-Type: application/json' \-d '{"profileUrls":["22656"],"maxProfiles":1}'
Poll the returned run ID until completion, then read its defaultDatasetId and defaultKeyValueStoreId reports. In n8n use an HTTP Request node with the same URL, Bearer token and JSON body. The permanent Actor ID avoids depending on its historical stackowerflow-scraper slug spelling.
MCP and AI agents
Connect the hosted Apify MCP server and select apivault_labs/stackowerflow-scraper (Actor ID I2ZH6abZW68mjgh01). Ask the agent:
Run this Actor for Stack Overflow users 22656 and 1144035, maxProfiles 2. Wait for completion, then read Dataset plus SUMMARY, ERRORS and WARNINGS. Report reputation, separate answer/question counts, public website and top contribution tags. Say whether enrichment was partial. Do not infer missing email, private identity or current availability for recruiting.
Actor input is the same through the UI, API and MCP. Apify authentication is required.
Pricing
- $0.0028 per useful profile ($2.80 per 1,000 profiles).
- $0.00005 Actor start event per allocated GB, minimum one event. At the default 256 MB this is $0.00005 per run.
- No profile events for duplicates, capped input, errors or empty results.
- Platform usage is separate under the configuration active since October18,2026 at19:31UTC (22:31 Minsk); event rates remain unchanged.
One delivered profile currently has $0.00285 in Actor events. Add actual platform usage; there is no guaranteed all-in unit cost. Credit availability and platform plan limits vary, so no fixed number of free profiles is promised.
FAQ
Does the official API require a key? Public read methods used here work without a Stack Exchange key. Anonymous access has a shared limited quota and cached responses. Apify API access still requires your Apify token.
Can it find developers by skill? Supply known profile URLs/IDs. The Actor returns their top contribution tags; it does not search the developer directory or judge employment skills.
Does every profile contain an email? No. The source has no public account-email field. Only an address explicitly written in the public bio or mailto link is extracted. Missing email is normal.
Can it return a private profile or Stack Overflow Teams data? No. Public Stack Overflow profiles only.
Why keep the old slug? Existing API/MCP integrations use it. The title and documentation use the correct Stack Overflow spelling; the permanent Actor ID is stable.
Source documentation: users by ID, user fields, custom filters, quota/backoff. This Actor is independent of Stack Overflow and Stack Exchange.
Enrich a known developer profile shortlist
This Stack Overflow profile scraper is useful when you already have a set of public user IDs and want consistent contribution context. It can help with community research, attribution and a reviewed developer directory. It does not search for people by profession, verify legal identity or decide whether a person is available for a job.
| Research goal | Input approach | Review before using the result |
|---|---|---|
| Known profile lookup | One user ID | userId, name, reputation and source status |
| Contribution comparison | Small list of IDs | Separate answer/question counts and optional tag coverage |
| Public directory enrichment | Selected profile fields | Attribution and the difference between display and legal names |
| Repeat public observations | Save dated snapshots externally | Source caching and shared API quota |
Look up one known public user
{"profileUrls": ["22656"],"maxProfiles": 1,"maxConcurrency": 1,"timeout": 90}
Check identityValidated and userId. The public display name is not a verified legal name. Reputation is an API contribution metric, not a follower count or a professional qualification.
Compare two contribution profiles
{"profileUrls": ["22656","1144035"],"maxProfiles": 2,"maxConcurrency": 1}
Read separate answerCount and questionCount values, plus WARNINGS for optional enrichment. Do not rank professional ability from a single reputation value or the first five tags.
Keep public bio and website context without email extraction
{"profileUrls": ["https://stackoverflow.com/users/22656/jon-skeet"],"maxProfiles": 1,"extractEmail": false,"extractCategory": false,"extractMetadata": false,"maxConcurrency": 1}
Disabling category and metadata avoids requesting their tag fields. Public bio text can still contain an address literally written by its author; extractEmail false is a field toggle, not a personal-data redaction tool.
Deduplicate alternate forms of the same profile
{"profileUrls": ["22656","https://stackoverflow.com/users/22656/jon-skeet"],"maxProfiles": 1,"extractBio": false,"extractEmail": false,"maxConcurrency": 1}
Canonical identity deduplication keeps one useful profile in this run. A new run can return and charge a new snapshot of the same user; there is no built-in cross-run change-only monitor.
Interpret the developer data and total cost
Preserve userId, attributionUrl, source and observedAt when exporting a reviewed profile list. The legacy extractFollowers input controls reputation; it does not expose a hidden follower count. fullName repeats the public display name. An absent public email is normal, and an extracted literal email is not a verified or necessarily current contact channel. Missing source counts remain unknown rather than being replaced by guessed zeros.
The current result rate is $0.0028 per useful profile ($2.80 per1,000), with startup $0.00005 per allocated GB, minimum one event. Platform usage is separate under the configuration active since October18. Two profiles cost $0.0056 in profile events before startup and resources. Optional top-tag work can consume requests without adding a paid profile. A core profile with enrichment warnings can be useful, but it is not a complete successful enrichment.
Use SUMMARY.apiRequests and quotaRemaining with ERRORS/WARNINGS to understand coverage. Source responses can be cached, anonymous quota is shared, and the Actor honors backoff. More concurrent workers do not grant extra source quota. A retry can deliver and charge the core profile again even when the previous run already collected it; review existing rows and retry advice before rerunning. No unlimited-throughput or real-time freshness claim is made.
JSON retains metadata and top-tag counts; a CSV projection is useful for profile IDs, reputation and contribution totals. The existing n8n/Python links below use the stable Actor identity. Keep the historical slug spelling in saved API integrations unless you intentionally switch to the permanent Actor ID.
Are top contribution tags verified job skills? No. They summarize available Stack Overflow contributions within the supported five-tag limit, with partial coverage reported explicitly.
Does a failed lookup mean a developer has no contributions? No. Missing profiles, source quota and request failures are separate from the person's actual activity. Keep those errors out of numerical contribution comparisons.
n8n and developer integrations
Use this Actor in your automation or application with the existing community integrations below. An Apify account and API token are required; Actor and platform charges follow the current pricing.
- n8n community node: n8n-nodes-apivault-stackoverflow. Install package name
n8n-nodes-apivault-stackoverflowin a self-hosted n8n instance that permits community packages. - n8n community node: n8n-nodes-apivault-stackowerflow-scraper. Install package name
n8n-nodes-apivault-stackowerflow-scraperin a self-hosted n8n instance that permits community packages. - Python client and examples: GitHub.
- n8n source and usage: GitHub.
- n8n source and usage: GitHub.
These are community packages. Publication on npm does not establish n8n verification or availability in n8n Cloud. Review the linked package README for supported inputs and setup.