Skip to content
POST/repos/{owner}/{name}/issues/{number}/comments

On a pull request, give path and line to comment on one line of the change.

  • Authentication: Required. Send an access token as Authorization: Bearer.
  • MCP tool: add_comment, with the same inputs
Name Type Required Description
owner string Yes The workspace that owns the repository.
name string Yes The repository’s name.
number integer Yes The number shown after the #. Issues and pull requests share one sequence.

Send a JSON object. Names are snake_case, as in responses; the camelCase spelling is accepted too.

Name Type Required Description
body string Yes Markdown.
path string No On a pull request: the file to comment on.
line integer No The line of that file, as numbered after the change.
curl -X POST https://api.g1t.sh/repos/flagon-io/hello/issues/12/comments \
-H "Authorization: Bearer $G1T_TOKEN" \
-H "Content-Type: application/json" \
-d '{
"body": "Should an empty name fall back to \"world\"?"
}'

A successful request answers 200 with:

{
"id": "cmt_01m43sv4c8e2g6j0m4q8t2x6a1",
"kind": "comment",
"author": {
"id": "usr_01kkntcg1eeb98j62xjm7eh09p",
"username": "syntaqx",
"kind": "user",
"verified": true,
"workspaces": [
{
"slug": "flagon-io",
"role": "owner"
}
]
},
"body": "Should an empty name fall back to \"world\"?",
"path": null,
"line": null,
"verdict": null,
"created_at": "2026-10-01T18:12:30.551Z"
}

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.
409 conflict The request conflicts with the current state.
422 invalid The input is not valid. message says which field and why.