GitLab project releases

GET https://api.api.sh/gitlab/v1/project/releases
1 credit / call reference try it in the playground →

Releases of a public gitlab.com project, newest first: name, tag, link, release and creation dates, upcoming flag, author, commit, milestones, release notes (first 8,000 characters) and assets (packages and source archives). Pass next_page back as page; null on the last page.

Every response includes credits_used: the credits this call cost.

Parameters

nametypedescription
pathrequired string Project path (namespace/project), its gitlab.com link, or the numeric project id. Example: gitlab-org/gitlab-runner
order_by released_at | created_at released_at (default) or created_at.
sort desc | asc desc (default) or asc.
page integer Page number (default 1).
limit integer Results per page (default 20, max 100).

Every endpoint also takes fresh, raw, fields (see lean responses and caching).

Example

curl "https://api.api.sh/gitlab/v1/project/releases?path=gitlab-org%2Fgitlab-runner" \
  -H "x-api-key: $APISH_KEY"

Response

A JSON object with the fields described above, plus raw (the source's own data), cached, fetched_at and credits_used. Errors return {"success": false, "error": "…"} with the HTTP status (see errors). A lookup that ran but found nothing (404) costs the price above; refused calls and errors on our side are free (what's charged).

The fastest way to see the full response is the playground: it runs this endpoint with your account and shows the exact JSON.