Set a thread subscription

Subscribe to an issue or pull request (subscribed, true unless you say), unsubscribe (subscribed false), or ignore it (ignored true): hear of nothing on it, not even a mention.

PUT/notifications/threads/{id}/subscription

Unsubscribed, you still hear of what is asked of you (a review, an assignment, a mention, an agent waiting on you), and commenting or being mentioned subscribes you again. Name it by a thread’s id, or by repo and number. Returns your subscription.

Body	Then
`{}` or `{"subscribed": true}`	You hear of what happens on it
`{"subscribed": false}`	You hear only of what is asked of you
`{"ignored": true}`	You hear of nothing on it, not even a mention

Authentication: Required. Send an access token as Authorization: Bearer.
MCP tool: notifications with action subscribe, and the same inputs
Scope: An access token needs notifications:write.
Also at: PUT /repos/{owner}/{name}/issues/{number}/subscription

Path parameters

Name	Type	Required	Description
`id`	string	Yes	A thread’s id, from `list_notifications`. Or give repo and number.

Body parameters

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

Name	Type	Required	Description
`number`	integer	No	With repo: the issue or pull request’s number.
`subscribed`	boolean	No	True (the default) to subscribe, false to unsubscribe.
`ignored`	boolean	No	True to hear of nothing on it, not even a mention.

Example request

curl -X PUT https://api.g1t.sh/notifications/threads/ntf_01kp7m2q3r4s5t6v7w8x9y0z1a/subscription \
  -H "Authorization: Bearer $G1T_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "ignored": true
  }'

Example response

A successful request answers 200 with:

{
  "subscribed": false,
  "ignored": true,
  "reason": null,
  "repo": "flagon-io/hello",
  "number": 14,
  "updated_at": "2026-10-07T10:04:00.000Z"
}

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