GitHub Developer Scraper β Find Devs by Location & Language
Pricing
from $1.70 / 1,000 results
GitHub Developer Scraper β Find Devs by Location & Language
Find developers on GitHub by location, programming language, keyword and follower count. Export each enriched with name, company, location, website, email and X/Twitter. Build targeted developer and recruiting lead lists β no code or token required.
Pricing
from $1.70 / 1,000 results
Rating
0.0
(0)
Developer
Haketa
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
1
Monthly active users
4 days ago
Last modified
Share
π§βπ» GitHub Developer Scraper
Find developers on GitHub by location, language and followers β as an enriched lead list.
Search GitHub's millions of developers by location, programming language, keyword and follower count β and export each one enriched with name, bio, company, location, website, public email and X/Twitter. It's the fastest way to build a targeted list of real, active developers for recruiting, sales or research.
π No token, no login, no code. Pick your filters and press Start. A GitHub token is optional and only speeds up very large jobs.
β¨ Why you'll love it
- π― Precisely targeted β combine location + language + follower filters to reach exactly the developers you want.
- π§βπ» Real, enriched profiles β name, company, location, website, X/Twitter and follower count in every row.
- π Ranked by influence β results come sorted by follower count, so your best leads are at the top.
- π Worldwide β find Python developers in London, Go developers in Berlin, or the most-followed developers on the planet.
- π Works without a token β many competitors force you to create API keys. This one doesn't.
- π§Ή Clean, deduplicated output β spreadsheet-ready, only the columns that matter.
π₯ Who it's for
| You are⦠| Use it to⦠|
|---|---|
| π§² Technical recruiter | Source engineers by language, location and activity β with contact links. |
| π οΈ Dev-tool / SaaS marketer | Build lists of developers in your exact target segment. |
| π Founder / DevRel | Find and reach developers for beta programs, communities and outreach. |
| π Market researcher | Map the developer population of a technology or region. |
| π€ Agency / consultancy | Build targeted outreach lists of engineers in a niche. |
β‘ Quick start
- Open the Actor.
- Set any combination of filters β e.g. Location =
London, Programming language =Python, Minimum followers =500. - Press Start. (Leave everything empty for a ready-made sample of the most-followed developers.)
- Open the Output tab to preview.
- Hit Export β Excel / CSV / JSON, or send to Google Sheets, Airtable, Zapier, Make, or your app via API.
π§© Input options (all optional)
π€ Keyword Β· keyword
Words to match in a developer's name, username or bio β e.g. machine learning, devrel, game developer.
π Location Β· location
City, region or country β e.g. London, Berlin, San Francisco, India. Leave empty for worldwide.
π» Programming language Β· language
Pick a language from the dropdown to only return developers whose top language matches.
π₯ Minimum followers Β· minFollowers
Only developers with at least this many followers β a strong signal of influence.
π¦ Minimum public repositories Β· minRepos
Only developers with at least this many public repositories.
π·οΈ Account type Β· accountType
Return individual developers, organizations, or both.
π’ Max developers Β· maxItems
How many developers to collect. GitHub search returns up to 1,000 matches per set of filters.
π GitHub token Β· githubToken (optional)
Not needed. Add a free personal access token only to run very large jobs faster.
π Proxy Β· proxyConfiguration
Recommended and on by default. Standard datacenter proxies are enough.
π§ͺ Example inputs
π€ Output
Every developer is one flat, spreadsheet-ready row. Only the fields that exist for a given profile are included, so your export stays clean.
π Field reference
| Field | π Description |
|---|---|
username | π§βπ» The developer's GitHub username. |
name | Their display name. |
bio | Profile bio. |
company | π’ Company / organization (often an @handle). |
location | π Location. |
websiteUrl | π Personal or company website. |
email | βοΈ Public email β included when the developer made it public. |
twitter | π¦ X / Twitter handle. |
followersCount | π₯ Follower count (results are sorted by this). |
followingCount | How many accounts they follow. |
publicRepos | π¦ Public repositories (with token enrichment). |
hireable | β Whether they flagged themselves open to work (with token enrichment). |
createdAt | π When they joined GitHub (with token enrichment). |
avatarUrl | πΌοΈ Avatar image. |
profileUrl | π Link to their GitHub profile. |
type | User or Organization. |
π§βπ» Sample row
{"username": "peterbourgon","name": "Peter Bourgon","bio": "Go, distributed systems, klichΓ©.","location": "Berlin","websiteUrl": "https://peter.bourgon.org","twitter": "peterbourgon","followersCount": 3200,"profileUrl": "https://github.com/peterbourgon","type": "User"}
π‘ Use cases in detail
π§² Source engineers with exact skills Set the language and location to your requirements, add a follower or repo minimum for quality, and export a ranked shortlist of active developers β each with a website or X handle to reach them on.
π οΈ Target developers for your tool Build a list of, say, TypeScript developers with 100+ followers, then reach the exact segment most likely to adopt your product.
π Grow a community or beta Find developers in a technology or region and invite the most active and influential ones first.
π Research a developer market Quantify and map the developers using a language or living in a region, by company and location.
π§ Tips for best results
- π― Combine filters β location + language + minimum followers gives the most targeted, highest-quality list.
- π Results are ranked by followers β the most influential developers appear first.
- π Vary your filters β GitHub returns up to 1,000 matches per filter set, so run several targeted searches to go wider.
- π§Ή Deduplication is automatic within each run.
π Export & integrations
β¬οΈ Excel Β· CSV Β· JSON Β· XML Β· π Google Sheets & Airtable Β· π Webhooks & API Β· π€ Make, Zapier, n8n
β FAQ
Do I need a token? β No. The Actor runs fully without one. A token is optional and only speeds up very large jobs.
Do I need to write a search query? β No. Just fill in the friendly filters and the Actor builds the search for you.
Are emails always included? β Only when a developer has made their email public, so expect it on a minority of rows. Website and X/Twitter are more commonly available.
How many developers can I get? β GitHub search returns up to 1,000 matches per set of filters. Run several targeted searches (by location, language, etc.) to cover more.
Will I get duplicates? β No. Developers are deduplicated within each run.
Can I schedule it? β Yes. Use Apify Schedules to refresh your lists daily, weekly or monthly.
βοΈ Legal & responsible use
This Actor collects only publicly available profile information for legitimate research, recruiting and lead generation. You are responsible for how you use the data, including compliance with applicable laws (such as GDPR and CCPA), platform terms, and anti-spam rules when contacting anyone. Do not use the data for unsolicited bulk messaging or any unlawful purpose, and always respect the privacy and preferences of the people in your results.