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, star, fork, language, and release data as JSON.
Endpoint families
5
Documented params
69
Examples
16
Live catalog snapshot
Active endpoints
16
Methods
GET
Required params
36
Schema refs
16
{
"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, star, 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/repo/{owner}/{repo}
/github/user/{username}
/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
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.
Business & Market Intelligence
Use a LinkedIn API to collect public company, profile, and search signals as structured JSON through documented LinkedIn API endpoints — called with one Crawlora API key, with no separate LinkedIn API key or scraper to maintain — for B2B enrichment, professional research, and lead discovery workflows.