GitHub
GET /v1/github/trending-developers

GitHub Trending Developers API

github.com/trending/developers — windowed ranks with popularRepo + followers (2 credits).

2 credits per request
TL;DR
github.com/trending/developers — windowed ranks with popularRepo + followers (2 credits). The GitHub Trending Developers API (GitHub) is a single authenticated GET request to /v1/github/trending-developers that responds with clean JSON and costs 2 credits. Pass cache=true for a free 24h cache hit; default is always fresh. Start with 100 free credits — no credit card.

What is the GitHub Trending Developers API?

Scrapes github.com/trending/developers (source: "github.com/trending/developers") for developers ranked in a since=daily|weekly|monthly window — not REST /search/users with followers:>1000 (all-time most-followed). Each row: rank, login, name, url, avatar, popularRepo/popularRepoUrl/popularRepoDescription, plus followers, following, bio, company, location, publicRepos, ownerType hydrated from GET /users/{login}. No Search relevance score field. Flat 2 credits. Page usually ≤25 rows (no cursor).

What you get

  • Real github.com/trending/developers (not followers:>1000 search)
  • since window + popularRepo from the page
  • followers/bio/company/location for ranking and vetting

Platform limits

Honest ceilings from the upstream platform surface — not Captapi bugs. Unexpected truncation here is usually the platform, not us.

  • Hydration uses GitHub REST /users/{login} per row — profile fields may be omitted if GitHub rate-limits.
  • Page usually has ≤25 rows — no cursor.

Try it

Open in Playground

Fill in the parameters below and copy a ready-to-run request, or open the live Playground to run it against your account (no API key paste).

Parameters

Sign in to run live
curl "https://api.captapi.com/v1/github/trending-developers?since=daily" \
  -H "Authorization: Bearer capt_live_..."
# or: -H "x-api-key: capt_live_..."

Edit the parameters and the code updates instantly. Switch languages and hit copy.

Example response

{
  "success": true,
  "data": {
    "source": "github.com/trending/developers",
    "since": "weekly",
    "totalReturned": 2,
    "developers": [
      {
        "platform": "github",
        "type": "developer",
        "rank": 1,
        "login": "getify",
        "name": "Kyle Simpson",
        "url": "https://github.com/getify",
        "avatar": "https://avatars.githubusercontent.com/u/150330?v=4",
        "popularRepo": "getify/You-Dont-Know-JS",
        "popularRepoUrl": "https://github.com/getify/You-Dont-Know-JS",
        "popularRepoDescription": "A book series on JS",
        "since": "weekly",
        "followers": 45221,
        "publicRepos": 74,
        "bio": "Human-Centric Technologist",
        "location": "Austin, TX",
        "ownerType": "User"
      },
      {
        "platform": "github",
        "type": "developer",
        "rank": 2,
        "login": "sindresorhus",
        "name": "Sindre Sorhus",
        "url": "https://github.com/sindresorhus",
        "avatar": "https://avatars.githubusercontent.com/u/170270?v=4",
        "popularRepo": "sindresorhus/awesome",
        "popularRepoUrl": "https://github.com/sindresorhus/awesome",
        "since": "weekly",
        "followers": 70000,
        "publicRepos": 1200,
        "ownerType": "User"
      }
    ]
  }
}

Billing metadata is returned in response headers: X-Captapi-Credits (credits charged), X-Captapi-Cache (hit or miss), and X-Captapi-Source. Failed requests (4xx/5xx) are never charged. See the full list of error codes in the error reference.

Response structure

A successful call returns success, cached, creditsUsed, and a data object with the following fields:

Top-level fields

  • sourceAlways "github.com/trending/developers" — not REST /search/users.
  • sinceTrending window echoed from the request: daily | weekly | monthly.
  • totalReturnedNumber of items returned in this response.

Developers

Each item in developers contains:

  • platformPlatform identifier for this response (matches the endpoint's platform).
  • typeContent type of the item.
  • rank1-based position on the trending developers page.
  • loginAccount login name.
  • nameName of the item or account. On profile endpoints: deprecated alias of displayName (one release).
  • urlCanonical URL of the item.
  • avatarAvatar / profile picture URL. Canonical across profile endpoints.
  • popularRepoowner/name of the popular repo shown on the trending card.
  • popularRepoUrlPopular repo url URL.
  • popularRepoDescriptionPopular repo description. Example: "A book series on JS".
  • sinceTrending window echoed from the request: daily | weekly | monthly.
  • followersFollower count hydrated from GET /users/{login} (the ranking signal you can sort on).
  • publicReposPublic repository count from the hydrated profile.
  • bioPublic profile bio when set.
  • locationLocation shown on the profile or item.
  • ownerTypeOwner type. Example: "User".

Parameters

NameTypeRequiredDescription
sincestringNoTrending window: daily (default), weekly, or monthly — matches github.com/trending/developers?since=.
languagestringNoOptional programming-language slug → /trending/developers/{language}.
limitintegerNoMax items to return (default 25, max 100). Flat 2 credits per call.
cachebooleanNoSet true to serve from the 24h response cache (0 credits on hit). Default false — always fetch fresh. Envelope includes cached + cachedAt on hits.

Authentication: send your key as Authorization: Bearer capt_live_.... A typical call costs 2 credits. Pass cache=true for a free 24h cache hit; default is always fresh.

Using an AI agent? This endpoint is the MCP tool github_trending_developers via @captapi/mcp. Set it up →

How it works

  1. 1. Sign up — get 100 free credits, no card required.
  2. 2. Create a key from your dashboard.
  3. 3. Send one request to /v1/github/trending-developers and parse the JSON response.

Use cases

Windowed discovery

Rank developers from github.com/trending/developers by since=daily|weekly|monthly — not all-time follower search.

Popular repo signal

Read popularRepo + description from the trending card, then open github/repository for detail.

Hiring shortlist

Filter hydrated followers, publicRepos, location, and bio without a second profile call.

Frequently asked questions

What does the GitHub Trending Developers API do?+

The GitHub Trending Developers API lets you search and return matching results from a public GitHub query using one GET request to /v1/github/trending-developers. It returns clean JSON — no OAuth or infrastructure setup required.

How many credits does the GitHub Trending Developers API cost?+

Each successful call costs 2 credits. Pass cache=true to serve from the 24h cache (0 credits on hit); default is always fresh. Hits include cached + cachedAt. Selected profile endpoints also accept cacheMaxAge=1d|3d|7d|14d|30d. Failed or empty results are never charged.

Do I need a GitHub API key or OAuth?+

No. A single Captapi key works across every platform Captapi supports — YouTube, TikTok, Instagram, Facebook, Twitter/X, Reddit, Threads, Bluesky, Pinterest, LinkedIn, Rumble, Spotify, Kwai, and more. We handle proxies, rate limits, retries, and authentication for you.

Is this followers:>1000 user search?+

No. That returns all-time most-followed accounts. This scrapes github.com/trending/developers for a since window and hydrates followers/bio from /users/{login}. There is no Search relevance score field.

Is the GitHub Trending Developers API suitable for production use?+

Yes. It is a stable REST endpoint with predictable JSON and automatic retries. Pass cache=true to serve from the 24h cache (0 credits on hit); default is always fresh. Hits include cached + cachedAt. Selected profile endpoints also accept cacheMaxAge=1d|3d|7d|14d|30d. Use it for analytics, monitoring, and content automation.

More GitHub APIs

Ready to use the GitHub Trending Developers API?

Sign up, grab your key, and make your first call in 60 seconds.