Skip to content

scrapeatlas.Dashboard

Developer communities

GitHub API

GitHub search, profiles, repositories, trending projects, pull-request sections, code activity and repository reports.

16 endpointsx-api-key

Discover projects and developers, chart repository growth, inspect pull requests and code, and retrieve public profiles, contributions, releases and issues.

API availability: Available

Base URL · local workerhttp://localhost:3021Public API: https://api.scrapeatlas.com.

Authenticationx-api-keyCustomer key from your account. See Authentication.

Endpoints

GET/v1/github/user

User

Retrieve a user or organization profile with biography, public email, location, account timestamps and counts; choose native, normalized or camelCase fields with format. Use view=social-links for linked social accounts or view=organizations for public organization memberships.

GET/v1/github/user/repositories

User repositories

List public repositories with owners, descriptions, stars, forks, topics, licenses and timestamps; choose native, normalized or camelCase fields with format and paginate with cursor or page. Use view=pinned for the repositories pinned on the profile, in displayed order.

GET/v1/github/user/pull-requests

User pull requests

List authored pull requests with repository, state and creation dates; choose native or camelCase fields with format. Use view=velocity with a handle for authored, merged and open totals in a creation-date window, with summary, repository or full enrichment.

GET/v1/github/user/connections

Connections

List a user’s followers or following with relationship=followers or following. Choose native or camelCase fields with format; continue with cursor.

GET/v1/github/user/contributions

Contributions

Retrieve daily contribution counts and intensity for a calendar year. Use view=activity for monthly activity with summaries, repositories and dates; its cursor steps back one month. Choose native or camelCase fields with format.

GET/v1/github/repository

Repository

Retrieve repository identity, owner, stars, forks, subscribers, topics, license and feature flags; choose native, normalized or camelCase fields with format. Use view=languages for language byte shares, view=report for metadata with README, recent releases and top issues, or view=top-issues for the most-reacted and most-discussed issues.

GET/v1/github/trending

Trending

Discover trending repositories or developers with type=repositories or developers, programming language and daily, weekly or monthly periods.

GET/v1/github/repo/releases

Releases and tags

One source page of releases with tags, names, Markdown notes, publication dates, prerelease flags, author and asset metadata; asset files are not downloaded. Use type=tags or type=branches for repository tags or branches with commit references.

GET/v1/github/repo/issues

Issues

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.

GET/v1/github/issue

Issue

Retrieve issue or pull-request details from an /issues/N or /pull/N URL, with source fields and a type marker. Use section=comments for one page of discussion comments in creation order with text, author, reactions and timestamps.

GET/v1/github/search

Search

Search issues and pull requests, repositories or users with type=issues, repositories or users. Use source qualifiers, type-specific sorting and caller-selected pagination.

GET/v1/github/repo/contributors

Contributors

List repository contributors with public identity and contribution counts.

GET/v1/github/repo/commits

Commits

List dated commits with author, committer, message, parents and signature verification. Filter by branch, author, file path and date range.

GET/v1/github/repo/contents

Contents

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. Use view=readme for the repository README as text, or view=profile-readme with a handle or profile URL for a profile README.

GET/v1/github/repo/activity

Repository activity

Retrieve weekly and daily commit counts for repository activity charts. Use view=stars for weekly star totals and daily star counts; page through star history with cursor or page.

GET/v1/github/pull-request

Pull 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.

Quick start

Create an API key on your account page, then call the public API. Values below are placeholders.

Terminal

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 with a 16-request waiting queue (up to 8 seconds), 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.

Error codes

8

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 and the waiting queue are occupied.
504	`timeout`	Total deadline expired.