per_pageinteger
Results per page (max 100)
Default:30
pageinteger
Page number of the results to fetch.
Default:1
List check run annotations
Lists annotations for a check run using the annotation id. GitHub Apps must have the checks:read permission on a private repository or pull access to a public repository to get annotations for a check run. OAuth Apps and authenticated users must have the repo scope to get annotations for a check run in a private repository.
get
http://HOSTNAME/api/v3/repos/{owner}/{repo}/check-runs/{check_run_id}/annotations
Query Parameters
Path Parameters
ownerstringrequired
repostringrequired
check_run_idintegerrequired
check_run_id parameter
Response
200 application/json
Response
200 application/json
Response
Check Annotation
pathstringrequired
Example:README.md
start_lineintegerrequired
Example:2
end_lineintegerrequired
Example:2
start_columninteger | nullrequired
Example:5
end_columninteger | nullrequired
Example:10
annotation_levelstring | nullrequired
Example:warning
titlestring | nullrequired
Example:Spell Checker
messagestring | nullrequired
Example:Check your spelling for 'banaas'.
raw_detailsstring | nullrequired
Example:Do you mean 'bananas' or 'banana'?
blob_hrefstringrequired
get/repos/{owner}/{repo}/check-runs/{check_run_id}/annotations
Path Parameters
Query Parameters
200 application/json
Create a check suite
Note: The Checks API only looks for pushes in the repository where the check suite or check run were created. Pushes to a branch in a forked repository are not detected and return an empty pull_requests array and a null value for head_branch.
By default, check suites are automatically created when you create a check run. You only need to use this endpoint for manually creating check suites when you’ve disabled automatic creation using “Update repository preferences for check suites”. Your GitHub App must have the checks:write permission to create check suites.
post
http://HOSTNAME/api/v3/repos/{owner}/{repo}/check-suites
Path Parameters
ownerstringrequired
repostringrequired
Body
application/json
Body
application/json
head_shastringrequired
The sha of the head commit.
Response
application/json
Response
application/json
when the suite already existed
CheckSuite
A suite of checks performed on the code of a given code change
idintegerrequired
Example:5
node_idstringrequired
Example:MDEwOkNoZWNrU3VpdGU1
head_branchstring | nullrequired
Example:master
head_shastringrequired
The SHA of the head commit that is being checked.
Example:009b8a3a9ccbb128af87f9b1c0f4c62e8a304f6d
statusstring | nullrequired
Allowed values:queuedin_progresscompleted
Example:completed
conclusionstring | nullrequired
Allowed values:successfailureneutralcancelledskippedtimed_outaction_required
Example:neutral
urlstring | nullrequired
Example:https://api.github.com/repos/github/hello-world/check-suites/5
beforestring | nullrequired
Example:146e867f55c26428e5f9fade55a9bbf5e95a7912
afterstring | nullrequired
Example:d6fde92930d4715a2b49857d24b940956b26d2d3
pull_requestsarray | null[object]required
Show Child Parameters
appobject | nullrequired
GitHub apps are a new way to extend GitHub. They can be installed directly on organizations and user accounts and granted access to specific repositories. They come with granular permissions and built-in webhooks. GitHub apps are first class actors within GitHub.
Show Child Parameters
repositoryobjectrequired
Minimal Repository
Show Child Parameters
created_atstring | null(date-time)required
updated_atstring | null(date-time)required
head_commitobjectrequired
Simple Commit
Show Child Parameters
latest_check_runs_countintegerrequired
check_runs_urlstringrequired
rerequestableboolean
runs_rerequestableboolean
post/repos/{owner}/{repo}/check-suites
Path Parameters
Body
{
"head_sha": "d6fde92930d4715a2b49857d24b940956b26d2d3"
}
application/json
Update repository preferences for check suites
Changes the default automatic flow when creating check suites. By default, a check suite is automatically created each time code is pushed to a repository. When you disable the automatic creation of check suites, you can manually Create a check suite. You must have admin permissions in the repository to set preferences for check suites.
patch
http://HOSTNAME/api/v3/repos/{owner}/{repo}/check-suites/preferences
Path Parameters
ownerstringrequired
repostringrequired
Body
application/json
Body
application/json
auto_trigger_checksarray[object]
Enables or disables automatic creation of CheckSuite events upon pushes to the repository. Enabled by default. See the auto_trigger_checks object description for details.
Show Child Parameters
Response
200 application/json
Response
200 application/json
Response
Check Suite Preference
Check suite configuration preferences for a repository.
preferencesobjectrequired
Show Child Parameters
repositoryobjectrequired
Minimal Repository
Show Child Parameters
patch/repos/{owner}/{repo}/check-suites/preferences
Path Parameters
Body
{
"auto_trigger_checks": [
{
"app_id": 4,
"setting": false
}
]
}
200 application/json
Get a check suite
Note: The Checks API only looks for pushes in the repository where the check suite or check run were created. Pushes to a branch in a forked repository are not detected and return an empty pull_requests array and a null value for head_branch.
Gets a single check suite using its id. GitHub Apps must have the checks:read permission on a private repository or pull access to a public repository to get check suites. OAuth Apps and authenticated users must have the repo scope to get check suites in a private repository.
get
http://HOSTNAME/api/v3/repos/{owner}/{repo}/check-suites/{check_suite_id}
Path Parameters
ownerstringrequired
repostringrequired
check_suite_idintegerrequired
check_suite_id parameter
Response
200 application/json
Response
200 application/json
Response
CheckSuite
A suite of checks performed on the code of a given code change
idintegerrequired
Example:5
node_idstringrequired
Example:MDEwOkNoZWNrU3VpdGU1
head_branchstring | nullrequired
Example:master
head_shastringrequired
The SHA of the head commit that is being checked.
Example:009b8a3a9ccbb128af87f9b1c0f4c62e8a304f6d
statusstring | nullrequired
Allowed values:queuedin_progresscompleted
Example:completed
conclusionstring | nullrequired
Allowed values:successfailureneutralcancelledskippedtimed_outaction_required
Example:neutral
urlstring | nullrequired
Example:https://api.github.com/repos/github/hello-world/check-suites/5
beforestring | nullrequired
Example:146e867f55c26428e5f9fade55a9bbf5e95a7912
afterstring | nullrequired
Example:d6fde92930d4715a2b49857d24b940956b26d2d3
pull_requestsarray | null[object]required
Show Child Parameters
appobject | nullrequired
GitHub apps are a new way to extend GitHub. They can be installed directly on organizations and user accounts and granted access to specific repositories. They come with granular permissions and built-in webhooks. GitHub apps are first class actors within GitHub.
Show Child Parameters
repositoryobjectrequired
Minimal Repository
Show Child Parameters
created_atstring | null(date-time)required
updated_atstring | null(date-time)required
head_commitobjectrequired
Simple Commit
Show Child Parameters
latest_check_runs_countintegerrequired
check_runs_urlstringrequired
rerequestableboolean
runs_rerequestableboolean
get/repos/{owner}/{repo}/check-suites/{check_suite_id}
Path Parameters
200 application/json
List check runs in a check suite
Note: The Checks API only looks for pushes in the repository where the check suite or check run were created. Pushes to a branch in a forked repository are not detected and return an empty pull_requests array.
Lists check runs for a check suite using its id. GitHub Apps must have the checks:read permission on a private repository or pull access to a public repository to get check runs. OAuth Apps and authenticated users must have the repo scope to get check runs in a private repository.
get
http://HOSTNAME/api/v3/repos/{owner}/{repo}/check-suites/{check_suite_id}/check-runs
Query Parameters
check_namestring
Returns check runs with the specified name.
statusstring
Returns check runs with the specified status. Can be one of queued, in_progress, or completed.
Allowed values:queuedin_progresscompleted
filterstring
Filters check runs by their completed_at timestamp. Can be one of latest (returning the most recent check runs) or all.
Allowed values:latestall
Default:latest
per_pageinteger
Results per page (max 100)
Default:30
pageinteger
Page number of the results to fetch.
Default:1
Path Parameters
ownerstringrequired
repostringrequired
check_suite_idintegerrequired
check_suite_id parameter
Response
200 application/json
Response
200 application/json
Response
total_countintegerrequired
check_runsarray[object]required
A check performed on the code of a given code change
Show Child Parameters
get/repos/{owner}/{repo}/check-suites/{check_suite_id}/check-runs
Path Parameters
Query Parameters
200 application/json