Developer communities
GitHub API
GitHub search, profiles, repositories, trending projects, pull-request sections, code activity and repository reports.
Discover projects and developers, chart repository growth, inspect pull requests and code, and retrieve public profiles, contributions, releases and issues.
API availability: Available
http://localhost:3021Public API: https://api.scrapeatlas.com.Endpoints
/v1/github/userUser
Retrieve user or organization identity, biography, public email, location, account timestamps and counts. Choose native, normalized or camelCase fields with format.
Reference/v1/github/user/repositoriesUser repositories
List public repositories with owners, descriptions, stars, forks, topics, licenses and timestamps. Choose native, normalized or camelCase fields with format; paginate with cursor or page.
Reference/v1/github/user/pull-requestsUser pull requests
List authored pull requests with repository, state and creation dates. Choose native or camelCase fields with format.
Reference/v1/github/user/activityUser activity
Retrieve monthly contribution activity with summaries, repositories and dates. Choose native or camelCase fields with format.
Reference/v1/github/user/connectionsConnections
List a user’s followers or following with relationship=followers or following. Choose native or camelCase fields with format; continue with cursor.
Reference/v1/github/user/contributionsContributions
Retrieve daily contribution counts and intensity for a calendar year. Choose native or camelCase fields with format.
Reference/v1/github/repositoryRepository
Retrieve repository identity, owner, stars, forks, subscribers, topics, license and feature flags. Choose native, normalized or camelCase fields with format.
Reference/v1/github/trendingTrending
Discover trending repositories or developers with type=repositories or developers, programming language and daily, weekly or monthly periods.
Reference/v1/github/readmeREADME
Retrieve repository or profile README text. Use scope=repository with a repository URL, or scope=profile with a handle or profile URL.
Reference/v1/github/repo/releasesReleases
One source page of releases including tags, names, Markdown notes, publication dates, prerelease flags, author and release assets. Asset URLs are returned without downloading files.
Reference/v1/github/repo/issuesIssues
One page of issues and pull requests with title, body, author, labels, state, reactions, comment counts and timestamps. type filters the returned source page to issue, pr or all; pagination still follows the upstream page.
Reference/v1/github/issueIssue
Issue or pull-request details. Both /issues/N and /pull/N URLs use GitHub’s public issue resource. Source fields and a type marker are retained.
Reference/v1/github/issue/commentsComments
One page of issue discussion comments, ordered by source creation time, with text, author, reaction count and timestamps.
Reference/v1/github/searchSearch
Search issues and pull requests, repositories or users with type=issues, repositories or users. Use source qualifiers, type-specific sorting and caller-selected pagination.
Reference/v1/github/repo/dossierRepository report
Retrieve a repository report with metadata, README, releases and top issues. Choose section=full or top-issues to retrieve the corresponding report.
Reference/v1/github/user/profile-velocityVelocity
Retrieve authored, merged and open PR totals for a creation-date window, with selectable summary, repository or full enrichment.
Reference/v1/github/repo/star-historyStar history
Retrieve weekly repository star totals and daily star counts for growth charts.
Reference/v1/github/repo/languagesLanguages
Retrieve repository language byte counts and derived percentages.
Reference/v1/github/repo/contributorsContributors
List repository contributors with public identity and contribution counts.
Reference/v1/github/repo/commitsCommits
List dated commits with author, committer, message, parents and signature verification. Filter by branch, author, file path and date range.
Reference/v1/github/repo/contentsContents
Read repository directory entries or a file with its path, type, size, SHA, encoded content and source links. Select a branch, tag or commit with ref.
Reference/v1/github/repo/refsRepository refs
List repository tags or branches with type=tags or branches, including commit references and pagination.
Reference/v1/github/repo/activityRepository activity
Retrieve weekly and daily commit counts for repository activity charts.
Reference/v1/github/pull-requestPull request
Retrieve a pull request’s details, changed files, reviews, inline review comments or commits with section=details, files, reviews, comments or commits. Each list has its own pagination.
Reference/v1/github/user/social-linksSocial links
Retrieve public social-account links associated with a GitHub profile.
Reference/v1/github/user/organizationsOrganizations
List a profile’s public organization memberships with identity, description and avatar.
Reference/v1/github/user/pinnedPinned repositories
Retrieve repositories explicitly pinned on a public profile, preserving their displayed order, descriptions, languages and counters.
ReferenceQuick start
Create an API key on your account page, then call the public API. Values below are placeholders.
curl "https://api.scrapeatlas.com/v1/github/user?handle=example" \
-H "x-api-key: YOUR_API_KEY"Coverage & limits
- Stateless independent worker; four concurrent operations, 30-second deadline, 8 MiB combined decoded responses; one shared transient retry. No cookies, browser, database, credentials forwarded to GitHub or media downloads.
- Ordinary operations: at most two upstream attempts. Top issues: four. Repository dossier: eight. Profile velocity: 80. Composite operations report any auxiliary section that could not be read as an explicit partial result.
- Fixed HTTPS origins api.github.com and github.com only. Redirects are rejected. JSON is bounded to depth 32 and 100,000 nodes; HTML to depth 128 and 100,000 nodes.
- One page per listing, usually 30 and never more than 100 source records. Calendar graphs are at most 366 days. Trending pages are at most 100 records.
- SocialFetch aliases: /v1/github/profiles/{handle} and /repositories, /pull-requests, /activity, /followers, /following, /contributions beneath that path; /v1/github/repositories?url=... for a single repository. These return camelCase data payloads. Trending routes contain both payload shapes.
- Every response carries service accounting; issue, release and report payloads keep the source's rich fields.
| HTTP | failure.code | Meaning |
|---|---|---|
| 400 | invalid_request | Invalid, duplicate or unsupported parameters. |
| 401 | unauthorized | Invalid worker key. |
| 404 | not_found | Public source record unavailable; SocialFetch aliases return data.lookupStatus=not_found with HTTP 200. |
| 429 | upstream_rate_limited | GitHub throttled retrieval. |
| 502 | upstream_error upstream_challenged unsupported_page | Source retrieval failed or the source contract changed. |
| 502 | unsafe_redirect response_too_large payload_too_complex request_limit | A fixed safety or resource boundary was reached. |
| 503 | busy | All worker slots are occupied. |
| 504 | timeout | Total deadline expired. |