/github/users/repos

POST /api/github/users/repos

Price: 5 credits

List public repositories owned by a GitHub user

How to use it

List the public repositories owned by a GitHub user, most recently updated first. Returns id, name, description, language, star/fork/issue/watcher counts, topics, license, homepage, visibility, fork/archived/template/private flags, default branch, size, timestamps, and owner info.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• user string required — GitHub username (login) (examples: "torvalds", "octocat"; minLength: 1)
• count integer required — Number of repositories to return (min: 1)

Response

• @type string (default: "GithubRepoListItem")
• id integer required
• alias string required
• name string required
• description string nullable
• language string nullable
• star_count integer (default: 0)
• fork_count integer (default: 0)
• open_issue_count integer (default: 0)
• watcher_count integer (default: 0)
• topics array (default: [])
• license string nullable
• homepage string nullable
• visibility string (default: "")
• is_fork boolean (default: false)
• is_archived boolean (default: false)
• is_template boolean (default: false)
• is_private boolean (default: false)
• has_issues boolean (default: false)
• has_discussions boolean (default: false)
• default_branch string (default: "")
• size integer (default: 0)
• created_at string (default: "")
• updated_at string (default: "")
• pushed_at string (default: "")
• owner_alias string (default: "")
• owner_type string (default: "")
• owner_image string nullable
• web_url string (default: "")

Errors

• 422 — The request body did not validate Check the fields against this schema. A URN with the wrong prefix is the most common cause.
• 408 — The request ran past its time limit Raise `timeout` in the request body, up to the maximum this endpoint documents. Lowering `count` or turning off the `with_*` flags also helps, because less work finishes sooner.
• 412 — User not found Retrying will not help: either the entity does not exist, or the input points at a different one.
• 429 — Too many requests: a rate limit or a usage window is exhausted When the response carries an X-Retry-After header, wait that many seconds and retry: the same number is in the body as `detail.retry_after`, and the limit clears once that window passes. The message in the body names the limit that was hit.
• 500 — Something broke on our side Retrying will not help. If it keeps happening, send us the X-Request-ID from the response headers.
• 529 — Rate limit reached, or the endpoint is overloaded Wait at least 30 seconds, then retry.

Response headers

• X-Error — Error message text (present only on error)
• X-Request-ID — Unique request identifier
• X-Execution-Time — Execution time in seconds
• X-Result-Count — How many records the body carries. 0 means an empty result, which is a normal answer and not by itself an error. A non-zero count can come back together with X-Error when the failure happened partway through — read this header and X-Error independently.
• X-Total-Available-Results — How many records exist for this query, when the endpoint can say. On a `dry_run` request this is the answer and the body is empty. It saturates: the endpoint's documented maximum means 'at least that many', any smaller number is exact.
• X-Warning — Present when the request body carried keys this endpoint does not document. They were ignored, so any filter you meant to apply through them did not apply. Check the spelling against this schema and retry.
• X-Retry-After — Seconds to wait before retrying. Present only on 429.