Repository discovery
Use GitHub endpoints to turn repository discovery into repeatable API requests with documented inputs and JSON responses.
Turn public GitHub ecosystem signals into structured data for developer-market research, open-source intelligence, recruiting, and AI-agent workflows.
Search public GitHub repositories and users, track trending projects, and fetch repo, org, contributor, fork, language, and release data as JSON.
Endpoint families
5
Documented params
72
Examples
17
Live catalog snapshot
Active endpoints
17
Methods
GET
Required params
37
Schema refs
17
{
"platform": "GitHub",
"endpoint": "github-search-repositories",
"method": "GET",
"path": "/github/search/repositories",
"auth": "apiKey"
}Use cases
Search public GitHub repositories and users, track trending projects, and fetch repo, org, contributor, fork, language, and release data as JSON.
Use GitHub endpoints to turn repository discovery into repeatable API requests with documented inputs and JSON responses.
Use GitHub endpoints to turn open-source trend monitoring into repeatable API requests with documented inputs and JSON responses.
Use GitHub endpoints to turn developer and organization research into repeatable API requests with documented inputs and JSON responses.
Managed execution
Each Crawlora platform API is designed around a specific data surface. Instead of exposing a generic fetch endpoint, Crawlora combines endpoint-specific request logic, managed infrastructure, parsing, normalization, billing, and Playground-tested examples.
Request behavior is tuned for the target platform and endpoint type.
Supported endpoints can use managed proxy routing to improve reliability and reduce infrastructure work.
Dynamic pages can be routed through managed browser instances where JavaScript rendering is required.
Challenge pages and unusable upstream responses are detected and surfaced clearly.
Results are returned as documented JSON instead of raw HTML.
Test the same route from Docs and Playground before production integration.
Coverage map
These cards are generated from the active endpoint catalog, so the landing page reflects the same API surface used by Docs and Playground.
/github/user/{username}
/github/repo/{owner}/{repo}
/github/org/{org}
/github/search/repositories
/github/trending
Featured endpoints
/github/search/repositoriesSearches public GitHub repositories (market/competitive discovery). Unauthenticated search is rate limited to roughly 10 requests per minute.
/github/search/usersSearches public GitHub users (developer discovery). Unauthenticated search is rate limited to roughly 10 requests per minute.
/github/trendingReturns the repositories on GitHub's trending page (market discovery).
/github/trending/developersReturns the developers on GitHub's trending developers page (market discovery).
/github/user/{username}Returns a public GitHub user's profile plus user-published social links. Email is included only when the user has made it public on their profile.
/github/user/{username}/reposReturns a page of a user's public repositories (tech-stack signal).
Related APIs
Business & Market Intelligence
Collect public TrustMRR startup marketplace and leaderboard data as normalized JSON for startup research, SaaS discovery, and market intelligence workflows.
Business & Market Intelligence
Add website and competitive intelligence signals from SimilarWeb to research pipelines.
Business & Market Intelligence
Use a Brand Data API to turn any domain into a normalized brand profile — title, description, slogan, brand colors, logos and icons, social profiles, footer links, and schema.org organization data — as structured JSON for enrichment, branding, and research workflows.
Related dataset
Dataset · queryable JSON
Skip per-profile lookups: query ~973K enriched developer profiles in bulk — followers, company, interests, activity and clean geo — by country, stack, follower band or reachability over one REST call.
Explore the dataset →How to scrape GitHub
GitHub's REST API is well documented but rate-limits unauthenticated search to roughly 10 requests per minute, and it has no trending endpoint at all. Crawlora's 17 GitHub endpoints cover search, trending repositories and developers, and user, organization, and repository detail behind one key.
Search repositories or users by query with sort by stars, forks, or recency, or pull trending repositories and developers by language over a daily, weekly, or monthly window.
User and activity endpoints take a username, organization endpoints take an org, and repository endpoints take owner plus repo.
List endpoints take page and per_page, so contributors, forks, releases, followers, and following all iterate the same way.
Combine repository, language-breakdown, and contributor calls to build developer-market or open-source-intelligence tables, or start from the stored GitHub Users dataset for bulk profiles.
FAQ
GitHub's REST API is good and you should use it directly for authenticated work on your own repositories. These endpoints exist for the gaps: unauthenticated search is rate-limited to roughly 10 requests per minute, trending repositories and developers are a web page with no API behind them, and you would otherwise manage tokens and pagination per surface. Crawlora returns all of it as normalized JSON behind a single key.
Yes. Separate endpoints return trending repositories and trending developers, filtered by language and by a daily, weekly, or monthly window — data GitHub publishes as a web page but does not expose through its REST API.
For a repository: metadata, contributors, public forks, the language breakdown, and releases. For an account: profile, public repositories, pinned repositories, recent public activity, followers, and following.
Collecting publicly accessible repository and profile data is generally treated differently from accessing private repositories or logged-in account data, but it is not unconditional. Collect only public data, respect GitHub's terms and rate limits, and remember usernames and profile fields are personal data under GDPR and CCPA. This is not legal advice; review your local law before commercial use.