GitHub Scraper API
GitHub API: 12 endpoints for profiles, repos, READMEs, releases, issues, comments, and search — plus computed dossier, top-issues, and velocity endpoints. Standard calls cost 1 credit; 100 free credits, no card. One x-api-key replaces PAT creation, scoping, and rate-limit juggling, in the same JSON envelope as 41 other platforms.
TL;DR
The GitHub API by SocialCrawl returns GitHub data as structured JSON — 12 endpoints behind one x-api-key, from 1 credit per call. It shares one unified schema with 41 other platforms, so the same client code works everywhere.
Where to find SocialCrawl
Try the GitHub API in your browser
Type a real handle, run a real request, see the JSON SocialCrawl returns. No signup, no key — same response shape you get in production.
Try the GitHub Profile API
See real data before writing a single line
What data does the GitHub API return?
Every endpoint returns structured JSON with a unified schema. Computed fields like engagement rate and content category come standard.
Last updated June 2026
Get a GitHub user profile
Get a GitHub repository
List a GitHub user's repositories
Get a repository's README
List a repository's releases
List a repository's issues (and PRs)
Get a single issue or pull request
Get comments on an issue or pull request
Search GitHub issues and pull requests
Top feature request and top complaint for a repository
Full project dossier for a repository
User contribution velocity dossier
How do you scrape social media data in seconds?
The fastest social media scraping API for developers. Scrape profiles, posts, comments, and analytics from 42 platforms covering 10B+ monthly active users.
One schema, every platform
Query 42 platforms with identical response structures. Write your integration once.
Computed fields, not just scraped
Every response includes engagement_rate, estimated_reach, content_category, and language — ready to use.
See your data before you code
Visual Data Explorer — paste any URL, get rich result cards, sortable tables, CSV export.
import requests
response = requests.get(
'https://www.socialcrawl.dev/v1/tiktok/profile',
params={'handle': 'charlidamelio'},
headers={'x-api-key': 'sc_YOUR_API_KEY'}
)
data = response.json(){
"success": true,
"platform": "tiktok",
"data": {
"author": {
"username": "charlidamelio",
"followers": 152400000
},
"engagement": {
"likes": 12400000000,
"engagement_rate": 0.087
},
"metadata": {
"language": "en",
"content_category": "lifestyle"
}
}
}How does SocialCrawl handle 42 different platforms?
Social media scraping is hard. Schema normalization, authentication, rate limits, pagination — we handle it all before your data arrives.
Write once, query them all.
42 platforms return 42 different JSON shapes. We normalize every response into one consistent structure.
Metrics ready before you ask.
Engagement rate, estimated reach, content category, language — calculated on every response automatically.
One cursor, every platform.
Every platform paginates differently. We give you one consistent cursor-based system.
Live data, never cached.
Every request hits the actual platform. No stale data, no cache lag.
Auth, proxies, and rate limits — handled.
Platform authentication, IP rotation, rate limit management — abstracted away. Just send a GET request.
How does SocialCrawl compare to Official GitHub REST API for GitHub data?
Same GitHub data, two very different paths. Auth, rate limits, schema, and cost — side by side.
| Feature | SocialCrawl | Official GitHub REST API |
|---|---|---|
| Authentication | One x-api-key shared across 42 platforms | Personal access token (PAT) to create, scope, and rotate |
| Setup | Sign up, copy your key, send a GET — no app registration | Free, but you manage tokens per project and learn per-resource schemas |
| Rate limits | Managed upstream — no 403 retry logic to write | 5,000 requests/hour per authenticated token; you handle retries |
| Response schema | Unified data.items envelope shared with 41 other platforms | Different shape per resource; Base64 READMEs, Link-header pagination |
| Pricing | 1 credit standard, 5 advanced, 10 premium; 100 free credits, no card | Free within rate limits |
| Data coverage | Profiles, repos, issues, PRs, releases, plus AI dossier, top-issues, and velocity | Full raw resource coverage; no computed or AI-synthesized endpoints |
| Maintenance | Upstream changes absorbed by SocialCrawl for you | You own token rotation, pagination, and schema changes |
Authentication
Setup
Rate limits
Response schema
Pricing
Data coverage
Maintenance
How much does GitHub scraping cost?
SocialCrawl uses credit-based pricing: you pay per API call, and most GitHub endpoints cost just a few credits. Every account starts with 100 free credits — no subscriptions, no compute units, no credit card required.
See pricingIs GitHub scraping legal?
SocialCrawl returns publicly available GitHub data. Courts have generally upheld scraping public data — most notably in hiQ v. LinkedIn — but compliance depends on your use case and jurisdiction. You are responsible for following applicable laws and platform terms.
Have a question? We got answers
Find answers to frequently asked questions about SocialCrawl's API, pricing, and capabilities.
Contact usAsk AI about SocialCrawl
Ready to start scraping GitHub data?
Get your API key and access all 12 GitHub endpoints in under 60 seconds.
Start for free