Get a check suite

Get a check suite by id: cs_… for a reporter's, or a g1t Actions workflow run's id (run_…).

GET/repos/{owner}/{name}/check-suites/{id}

Authentication: Optional. Public data can be read without a token; send one to see what is private.
MCP tool: workflow with action get_check_suite, and the same inputs
Scope: An access token needs checks:read.

Path parameters

Name	Type	Required	Description
`owner`	string	Yes	The workspace that owns the repository.
`name`	string	Yes	The repository’s name.
`id`	string	Yes	The check suite’s id: cs_…, or a g1t Actions run’s run_…

Example request

curl https://api.g1t.sh/repos/flagon-io/hello/check-suites/cs_01kq4b7c8d9e0f1g2h3j4k5m6p \
  -H "Authorization: Bearer $G1T_TOKEN"

Example response

A successful request answers 200 with:

{
  "id": "cs_01kq4b7c8d9e0f1g2h3j4k5m6p",
  "head_sha": "9f3c2a1b7e6d5c4b3a2918f7e6d5c4b3a2918f7e",
  "head_branch": "main",
  "status": "completed",
  "conclusion": "failure",
  "app": {
    "slug": "buildkite",
    "name": "Buildkite"
  },
  "latest_check_runs_count": 1,
  "created_at": "2026-10-07T14:02:11.318Z",
  "updated_at": "2026-10-07T14:02:36.502Z"
}

Errors

A failed request answers with one of these statuses and a body like {"error": {"code": "not_found", "message": "Repository not found."}}. See errors.

Status	Code	When
401	`unauthenticated`	A token is required, or the one sent is not valid.
403	`forbidden`	The token is valid but not allowed to do this, such as a member-only change or an agent token outside its repository.
404	`not_found`	It does not exist, or you cannot see it.
422	`invalid`	The input is not valid. `message` says which field and why.