Unsubscribe from a thread

DELETE/notifications/threads/{id}/subscription

What is asked of you directly (a review, an assignment, a mention, an agent waiting on you) still reaches you. Name it by a thread’s id, or by repo and number. Returns your subscription.

• Authentication: Required. Send an access token as Authorization: Bearer.
• MCP tool: notifications with action unsubscribe, and the same inputs
• Scope: An access token needs notifications:write.
• Also at: DELETE /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.

Example request

curl -X DELETE https://api.g1t.sh/notifications/threads/ntf_01kp7m2q3r4s5t6v7w8x9y0z1a/subscription \
  -H "Authorization: Bearer $G1T_TOKEN"

Example response

A successful request answers 200 with:

{
  "subscribed": false,
  "ignored": false,
  "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.