Social Fetch
Get API key
GitHub hub

GitHub Trending Developers API

Pull the public GitHub trending developers list — optional language and time-window filters — as ranked JSON in Social Fetch's shared envelope.

GET /v1/github/trending/developers

1 credit per successful request.

Try in playgroundFull API docs

About this endpoint

Recruiting pipelines, open-source outreach, and developer-marketing agents often care who is rising on GitHub this week, not which repo gained the most stars. The people tab on github.com/trending is a ranked list of accounts; scraping that HTML is fragile, and GitHub's official REST/GraphQL APIs do not expose trending developers as a first-class list.

`GET /v1/github/trending/developers` returns that people list for the selected filters. Optional `language` narrows by programming language. Optional `since` is `daily`, `weekly`, or `monthly` (defaults to daily when omitted). The response echoes the applied `since` and `language` (null when unfiltered), then `developers` in rank order and `totalResults` matching that array length. Each row includes rank, handle, displayName, profileUrl, avatarUrl, and `popularRepository` when GitHub highlights one (owner, repo, fullName, url, name, description).

Credit pricing for this operation comes from the API registry and appears on this page; `meta.creditsCharged` is the billing source of truth. This route is developers only. For trending repos, use `GET /v1/github/trending/repositories`. For a known login's full profile card, use `GET /v1/github/profiles/{handle}`.

GitHub Trending Developers API FAQ

How do I list GitHub trending developers via API?

Call GET /v1/github/trending/developers with your Social Fetch API key in the x-api-key header. Optionally pass language and since (daily, weekly, or monthly). Full parameters and examples are in the API docs linked from this page.

What does the trending developers response include?

data.since and data.language echo the filters applied (null language when unfiltered). data.developers is the ranked list; data.totalResults matches that array length. Each developer row includes rank, handle, displayName, profileUrl, avatarUrl, and popularRepository when GitHub shows one. The shared envelope also carries meta.requestId and meta.creditsCharged.

How do since and language work?

since selects the trending window: daily, weekly, or monthly. Omitting since uses daily. language is an optional programming-language filter. Keep the same filters when you compare successive snapshots. This developers route has no spokenLanguageCode param (that filter exists on trending repositories).

How many credits does GitHub trending developers cost?

Pricing is documented on the operation in the API registry (shown on this page). Confirm on every response with meta.creditsCharged — that field is the billing source of truth.

Is this the same as trending repositories?

No. This endpoint lists trending developers (people), each of which may include an optional popularRepository. GET /v1/github/trending/repositories lists trending repositories. Use the route that matches the entity you need.

Does this endpoint paginate with a cursor?

No. The trending developers response returns one ranked list for the selected filters. There is no cursor or hasMore page object on this operation. If you need another window or language, call again with different query params.

Do I need a GitHub personal access token for trending developers?

No. Authenticate to Social Fetch with an API key only. You do not create a GitHub OAuth app or pass a personal access token for this public trending list.

Other GitHub endpoints