GitHub scraper API
Pull public GitHub profiles, repositories, activity, followers, contribution graphs, and trending lists over REST. Same JSON envelope as every other Social Fetch platform.
9 endpointsWhy teams use Social Fetch for GitHub
GitHub is the identity layer most social enrichment stacks forget. A founder on X, a maintainer on LinkedIn, and an open-source repo in a CRM note are three rows until you resolve the login, the public repos, the follower neighborhood, and whether that person is still shipping code. DIY scrapers of github.com HTML break on layout changes. Standing up your own GitHub App or personal access token stack just to hydrate public cards adds rate-limit plumbing, secret rotation, and a second client for a job that only needed read-only public fields.
Social Fetch exposes GitHub as ordinary GET routes. Pass a login for `GET /v1/github/profiles/{handle}`, a repository URL for `GET /v1/github/repositories`, or language and time-window filters for trending. Responses use the shared envelope: `data.lookupStatus`, `meta.requestId`, and `meta.creditsCharged`. Missing logins and unknown repos come back as typed `not_found` outcomes, not an empty 200 that looks like a successful hydrate.
The same API key covers Instagram, X, LinkedIn, and the rest of the marketplace catalog. A research agent or recruiting pipeline can attach a GitHub node to a person record without a second vendor, a second auth scheme, or a GitHub personal access token for these public lookups.
What GitHub data can you get?
- Profile cards by login — bio, company, location, follower and public-repo counts, User vs Organization.
- Single repository metadata by URL — stars, forks, language, license, topics, push timestamps.
- List public repositories for a user or org with pagination.
- Activity and yearly contribution graphs for shipping-signal enrichment.
- Followers and following lists for developer-graph expansion.
- Trending repositories filtered by language and daily / weekly / monthly window.
- Trending developers for discovery and open-source scouting jobs.
GitHub API endpoints
Grouped by capability from the live API catalog. Open an endpoint page for parameters and examples — credit notes come from OpenAPI pricing extensions.
Profiles & channels
1Lists & graphs
5Content
1Search & discovery
2How to call the GitHub API
1. Create an API key
Sign up at Social Fetch and copy a key (`sfk_…`). New accounts get 100 free credits — enough to exercise profile, repository, and trending routes against live data.
2. Call a GitHub route
Send `GET /v1/github/profiles/{handle}` (or any other GitHub path) with `x-api-key`. Use the playground for one-off checks; use the TypeScript SDK or curl in production jobs.
3. Read the shared envelope
Branch on `data.lookupStatus` before writing rows. Log `meta.requestId` for support. Bill against `meta.creditsCharged` — that field is the source of truth for what the call cost.
How much does the GitHub API cost?
GitHub marketplace routes document credit costs per operation (many profile and repository GETs are 1 credit on a successful completed lookup). List and trending calls can differ — read each operation page. Credits never expire on pay-as-you-go packs. Check `meta.creditsCharged` on every response.
Social Fetch vs the official GitHub API
GitHub's official REST and GraphQL APIs are first-class products. Use them (with a GitHub App or token) when you need webhooks, write operations, private repositories you are authorized to read, or deep GitHub-native automation. Social Fetch is a public-data lookup layer for enrichment and monitoring: login or repo URL in, structured JSON out, authenticated with your Social Fetch API key only — no GitHub personal access token for these public routes. Prefer official when GitHub is the product; prefer Social Fetch when GitHub is one node in a multi-platform Social Fetch pipeline.
GitHub API FAQ
Is there a GitHub scraper API that works without a personal access token?
Yes for Social Fetch public routes. You authenticate to Social Fetch with an API key (`x-api-key`). You do not create a GitHub OAuth app or pass a GitHub personal access token for public profile, repository, activity, follower, contribution, or trending lookups on this hub.
How do I fetch a GitHub profile with an API?
Create a Social Fetch key, call `GET /v1/github/profiles/{handle}` with the public GitHub login, and parse the JSON envelope. Branch on `data.lookupStatus` before treating the payload as a found profile. Docs and the profile endpoint page cover parameters and examples.
What GitHub data does Social Fetch cover?
Profiles, profile repositories, single repository by URL, activity, followers, following, contribution graphs, trending repositories, and trending developers. Exact paths live under `/docs/api` and on this hub's endpoint list.
Can I get trending GitHub repositories and developers?
Yes. `GET /v1/github/trending/repositories` and `GET /v1/github/trending/developers` accept language and time-window filters (daily, weekly, monthly where documented). Official GitHub REST does not expose the trending page as a first-class list endpoint.
How much does the GitHub API cost on Social Fetch?
You buy credit packs (or use the 100 free signup credits). Most GitHub GETs list a flat credit note per successful lookup; some list-style routes may differ. There is no required monthly subscription for pay-as-you-go packs. Trust `meta.creditsCharged` on each response.
Official GitHub REST API vs Social Fetch — what is the difference?
Official GitHub APIs are the right stack for authenticated GitHub apps, webhooks, private data you are authorized to access, and write operations. Social Fetch is a hosted public-lookup API with the same metering and envelope as TikTok, LinkedIn, and the rest of the marketplace. Choose official when you integrate deeply with GitHub; choose Social Fetch when GitHub is public enrichment beside other social sources on one key.
Are private repositories supported?
No. Social Fetch only returns publicly visible GitHub data. Private repos and non-public fields are never invented. Unknown logins and missing public repos resolve as `lookupStatus` `not_found`.
Can I pull contribution graphs and activity?
Yes. Contribution routes return yearly heatmap-style totals and per-day counts for a login. Activity routes cover public event-style signals. Paths are on this hub's endpoint list and in the API docs.
Can I expand a developer graph with followers and following?
Yes. Follower and following list routes take a public login and return publicly visible neighbor accounts for network expansion jobs. Pair them with the profile card when you need identity plus graph edges.
Can I use the GitHub API in production?
Yes. Routes are synchronous REST with typed errors, request IDs, and credit metering. Teams run recruiting enrichment, open-source monitoring, founder graphs, and agent tools against the documented routes.
Start with GitHub data
Create an account, spend the 100 free credits on live GitHub routes, then buy a pack when the JSON fits your pipeline. Credits do not expire on pay-as-you-go packs.