POST /api/github/repos
Price: 1 credit
Get GitHub repository details by owner/name or repository URL
Get full details of a GitHub repository by 'owner/name' slug or repository URL. Returns name, description, language, star/fork/issue/watcher/subscriber counts, topics, license, homepage, visibility, fork/archived/template/forking/issues/discussions flags, default branch, size, timestamps, and owner info.
access-token string requiredtimeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)repo string required — Repository in 'owner/name' format or full GitHub URL (examples: "anthropics/anthropic-sdk-python", "https://github.com/torvalds/linux"; minLength: 1)@type string (default: "GithubRepo")id integer requiredalias string requiredname string requireddescription string nullablelanguage string nullablestar_count integer (default: 0)fork_count integer (default: 0)open_issue_count integer (default: 0)watcher_count integer (default: 0)subscriber_count integer (default: 0)network_count integer (default: 0)topics array (default: [])license string nullablehomepage string nullablevisibility string (default: "")is_fork boolean (default: false)is_archived boolean (default: false)is_template boolean (default: false)allow_forking 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 nullableweb_url string (default: "")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 — Repository 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.X-Error — Error message text (present only on error)X-Request-ID — Unique request identifierX-Execution-Time — Execution time in secondsX-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.