GitHub User Scraper — Profiles, Followers & Hiring Signals

Look up GitHub users by login or profile URL, or search by location, language and follower count. One row per user: name, company, location, public email, bio, hireable flag, follower and repo counts, account age.

No API key required. $0.015 per profile — a login that does not exist, or a run that hits GitHub's limit, is recorded and not charged.

Input

{ "usernames": ["torvalds", "https://github.com/gaearon"], "maxUsers": 50 }

Search, then look each match up in full:

{ "searchQuery": "location:berlin language:go followers:>500", "maxUsers": 100 }

Field	Type	Notes
username	string	A login or a github.com/... profile URL.
usernames	string[]	Bulk logins or URLs.
searchQuery	string	GitHub user-search syntax — location:, language:, followers:>N, repos:>N.
maxUsers	integer	1–200 total. You are charged per profile returned.
githubToken	string	Optional — see Limits.

Output

{
  "ok": true,
  "foundVia": "lookup",
  "login": "torvalds",
  "name": "Linus Torvalds",
  "url": "https://github.com/torvalds",
  "company": "Linux Foundation",
  "location": "Portland, OR",
  "email": null,
  "blog": null,
  "twitterUsername": null,
  "bio": null,
  "hireable": null,
  "publicRepos": 12,
  "followers": 322271,
  "following": 0,
  "createdAt": "2011-09-03T15:26:22Z"
}

What it gets right

• Search returns full profiles. GitHub's search endpoint gives you logins and avatars and nothing else — no followers, company, email or bio. Each match is looked up properly, so a search result is the same rich row as a direct lookup, and foundVia tells you which path it came from.
• Profile URLs are resolved, not looked up verbatim, so pasting a link works.
• Logins are de-duplicated before any request — the same profile is never billed twice in one run, even if it appears in both your list and your search.
• ⚠️ The rate limit is surfaced, not hidden. See Limits. A run that hits it stops with a clear uncharged record naming the fix, instead of quietly returning half your list.
• Absent fields are null, never the string "null" — most profiles have no public email or company, and that is a real answer.

Pricing

$0.015 per profile returned. No start fee. Missing logins and rate-limit stops are recorded free.

Limits

⚠️ GitHub allows 60 requests per hour per IP without a token (10/min for search), and Apify runs from shared addresses, so that budget is not yours alone. Supply a free personal access token via githubToken to get 5,000/hour — create one at github.com/settings/tokens with no scopes at all; public profile data needs none.

• 200 profiles per run.
• Public profile data only. email is present only when the user has deliberately published one on their profile; most have not.
• hireable is the user's own flag, not an inference.
• Search matches GitHub's index, which lags profile edits slightly.

FAQ

Do I need a token? Not for small runs. For anything over ~50 profiles an hour, yes.

What scopes does the token need? None. Public data only.

Why is email usually null? Because most people do not publish one. This does not guess or harvest emails from commits.

Changelog

• 0.1 (2026-09-10) — first release. Bulk lookup, URL resolution, search-then-enrich, de-duplication, rate limit surfaced with optional caller token.