GitHub Trending API

POST

API health

24h health: Normal
24h average time: —

Healthy / normal
Available
Limited
Mostly down

Normal

Last 24 hours

Last 30 days

Read today's GitHub Trending list, usually about 14 repositories in ranked order, each with owner, name, link and description.

Price $0.81 per 1,000 requests ($0.000806 per call). Failed calls and empty results are not charged. Synchronous. For slow jobs add "mode": "async" to the body, take the job_id and poll.

AI prompt

Please help me write a data collection script with the EveryInfra GitHub Trending endpoint (github/trending).

How the endpoint works:
- Request: POST https://api.everyinfra.com/api/v1/social with the header Authorization: Bearer <API key>. Read the key from the EVERYINFRA_API_KEY environment variable and never hard-code it.
- In the request body, set platform to github and action to trending, and put the parameters inside params.
- No required parameters.
- Optional parameters:
  - limit: The most rows to return in this call, an integer from 1 to 25. The default applies when you leave it out, and a call can return fewer rows. Larger values return 422 before any charge. (default: 25)
- Returns a list of records. Main fields of each record: rank (Position in this response from 1: by co…), full_name (Repository name as owner/repo), owner_username (Username of the repository owner (user…), name, url, description.
- Example request body:
{
  "platform": "github",
  "action": "trending",
  "params": {}
}
- Price: $0.81 per 1,000 requests; failed and empty results are not charged.
- For dozens or hundreds of targets, add "mode": "async" to the body: you get a job_id at once and poll GET https://api.everyinfra.com/api/v1/jobs/{job_id} for the result.
- On 422, fix the request using the suggested parameter names and allowed values in the error; on 429 or 503, wait for Retry-After and try again.

Before writing code, ask me which targets I need, how many, which fields, and what output format I want; then confirm the plan and the rough cost with me.

Request parameters

Name	In	Type	Required	Default	Description
`Authorization`	header	`string`	Yes	-	Bearer followed by your API key. Create it in the console; never put it in a URL or a code repository.
`platform`	body	`string`	Yes	`github`	Platform identifier, fixed value.
`action`	body	`string`	Yes	`trending`	Capability identifier, fixed value.
`limit`	body.params	`integer (1–25)`	No	`25`	The most rows to return in this call, an integer from 1 to 25. The default applies when you leave it out, and a call can return fewer rows. Larger values return 422 before any charge.

Code samples

bash

curl -X POST 'https://api.everyinfra.com/api/v1/social' \
  -H "Authorization: Bearer $EVERYINFRA_API_KEY" \
  -H 'Content-Type: application/json' \
  --data-raw '{
  "platform": "github",
  "action": "trending",
  "params": {}
}'

OpenAPI definition (JSON)Samples read the key from the EVERYINFRA_API_KEY environment variable; copied code never contains your key.

Response example

Field preview

No sample response is available for these parameters yet. This preview shows the response shape and fields from the API definition, with … as placeholders; it is not the result of a live call.

json

{
  "id": "req_…",
  "platform": "github",
  "action": "trending",
  "results": [
    {
      "rank": …,
      "full_name": …,
      "owner_username": …,
      "name": …,
      "url": …,
      "description": …,
      "platform": …
    }
  ],
  "count": …,
  "billing": {
    "charged": …,
    "charged_usd": …,
    "balance_after_usd": …,
    …
  },
  "quota": { … }
}

Response fields

Business data is in results. The table lists the fields a record can contain; values the platform does not show are never made up.

Field	Meaning
`rank`	Position in this response from 1: by commit count for contributors, in Trending order for trending.
`full_name`	Repository name as owner/repo; a renamed or transferred repository shows its new name.
`owner_username`	Username of the repository owner (user or organization).
`name`	Name of the object itself, for account, product and business capabilities.
`url`	Link to the record on the platform.
`description`	Summary or description, usually shorter than text.
`platform`	Source platform identifier, the same as platform in the request (for example xiaohongshu, tiktok).

Errors and billing

401: Missing or invalid key.
402: Insufficient balance. Top up first.
422: Invalid parameter name or value. Fix it using the suggestions in the error. No charge.
429: Per-minute request limit reached. Wait for Retry-After, then try again.
503: Could not complete. The held charge is returned to your balance. If the outcome is unknown, verify it before you retry.
200 empty: No data. No charge.

Errors