/github/repos/releases

POST /api/github/repos/releases

Price: 20 credits

List releases of a GitHub repository by owner/name or repository URL

How to use it

List the releases of a GitHub repository by 'owner/name' slug or repository URL, newest first. Returns tag, name, changelog text, draft/prerelease flags, author, downloadable assets (name, size, download count, download URL), and timestamps. Set latest=true to return only the most recent published release.

Parameters

• access-token string required

Request body

• timeout 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: "facebook/react", "https://github.com/torvalds/linux"; minLength: 1)
• count integer required — Number of releases to return (min: 1)
• latest boolean — Return only the latest published release (default: false)

Response

• @type string (default: "GithubRelease")
• id integer required
• tag string required
• name string nullable
• text string nullable
• is_draft boolean (default: false)
• is_prerelease boolean (default: false)
• author string (default: "")
• assets array (default: [])
  • @type string (default: "GithubReleaseAsset")
  • id integer required
  • name string required
  • size integer (default: 0)
  • download_count integer (default: 0)
  • content_type string (default: "")
  • download_url string (default: "")
• created_at string (default: "")
• published_at 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 — 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.

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.