GitHub scraper API
Public GitHub profiles, repos, pull requests, activity, followers, contributions, and trending lists over REST — same envelope as every other platform.
Teams running monitoring, research, and enrichment pipelines
Why Social Fetch
We run the GitHub scrapers. You build the product.
Live GitHub data as JSON — proxies, platform changes and consistent output handled for you.
GitHub, plus every other network
One key and one response envelope for GitHub and 24 more platforms — profiles, posts, search, comments and transcripts.
Pricing you can reason about
One request, one credit. Know how far your balance will go before you run your next batch.
Live data on every request
Fetch public data when you ask for it — not from a shared cache.
No scraper maintenance
We handle proxies, browser changes, and platform breakages.
Built for production jobs
Run concurrent workloads with explicit statuses and request IDs.
Regular jobs. Better rates.
Running lookups every month? Get lower per-credit rates with a monthly plan. For occasional projects, choose pay as you go.
What GitHub data can you get?
10 endpoints, one API key. Every response comes back as live JSON in the same envelope.
Profiles & channels
Look up a GitHub account by handle or URL — bio, counts and metadata.
Lists & graphs
Page through an account's posts, videos, followers and more.
+1 more lists & graphs endpointsContent
Fetch a single post or video by URL, with metrics and media.
Search & discovery
Search GitHub by keyword, hashtag or trend.
Other
More GitHub routes on the same key.
Browse all 10 GitHub endpoints
Profiles & channels
Lists & graphs
Content
Search & discovery
Other
What teams build with GitHub data
Monitoring, enrichment, research and content workflows on GitHub data — the same API as every other platform.
How it works
Your first request in three steps.
Use TypeScript or your automation tool of choice.
Sources
+ 19 more platforms
One request
GET/v1/tiktok/profiles/
x-api-key: sk_live_••••••••
Same JSON shape
{
"data": {
"lookupStatus": "found",
"profile": {
"platform": "tiktok",
"handle": "charlidamelio",
"displayName": "charli d’amelio",
"verified": true
},
"metrics": {
"followers": 160263648
}
}
}Step 1
Create your free account
Get an API key with 100 requests included.
Step 2
Choose an endpoint
Pass a username, URL, keyword, or post ID.
Step 3
Get clean JSON
Use the response immediately or send it into your pipeline.
Works with your stack
Code, automate, or connect your AI.
TypeScript
n8n
- Make
- Apify
- MCP
- AI clients
Pricing
Social data, priced simply.
Start with 100 free credits. Monthly plans give you predictable volume and lower per-request rates.
Starter
18,000credits
$1.61 per 1k · $0.00161 per request
- Top up from $1.61 / 1k if you run out
- Up to 25 monitors
Growth
50,000credits
$1.58 per 1k · $0.00158 per request
- Top up from $1.58 / 1k if you run out
- 5 team seats
- Up to 100 monitors
Scale
150,000credits
$1.50 per 1k · $0.00150 per request
- Top up from $1.50 / 1k if you run out
- 25 team seats
- Up to 250 monitors
- Cancel anytime
- 30-day money-back guarantee
- Price locked while you stay
Need 1M+ credits, invoicing, or volume rates? Talk to us
Trust signals
DevHunt
Product Hunt
Uneed
Customers
Teams building on Social Fetch.
“Our TikTok and Instagram scrapers broke constantly. Social Fetch took us off that rotation — we ship product again.”
“Transcripts at volume from one endpoint. No broken scrapers for our small team to maintain.”
“Live profile data on every request. We never flag accounts from a stale cache.”
“Heavy concurrent load, no rate limits to negotiate. The rare API I haven't wrapped in retries.”
GitHub API: common questions
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, authored pull requests, 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 handle authenticated apps, webhooks, private data, and writes. Social Fetch is hosted public lookup with the same envelope as TikTok and LinkedIn. Choose official for deep GitHub integration; choose Social Fetch for 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.
The GitHub API in detailHow the GitHub routes work, what they cost, and how they differ from the official API.
Why teams use Social Fetch for GitHub
GitHub is the identity layer many enrichment stacks skip. Social Fetch exposes GitHub as GET routes: GET /v1/github/profiles/{handle}, GET /v1/github/repositories, or trending with language and time-window filters. Responses use { data, meta } with data.lookupStatus, meta.requestId, and meta.creditsCharged. Missing logins and unknown repos return typed not_found outcomes.
The same API key covers Instagram, X, LinkedIn, and the rest of the catalog — no second vendor or GitHub personal access token for these public lookups.
How 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) withx-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.lookupStatusbefore writing rows. Logmeta.requestIdfor support. Bill againstmeta.creditsCharged— that field is the source of truth for what the call cost.
What each GitHub route returns
- 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.
- List public pull requests authored by a GitHub user, newest first.
- 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.
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 REST and GraphQL APIs are first-class for webhooks, writes, private repos you authorize, and GitHub-native automation. Social Fetch is public read enrichment: login or repo URL in, structured JSON out, one Social Fetch API key. Use official APIs when GitHub is the product; use Social Fetch when GitHub is one node in a multi-platform pipeline.
Pull your first GitHub data.
Run a live GitHub request in the playground. 100 free credits, no card, JSON back in seconds.
No credit cardSign up in 30 seconds withGoogleGitHub