# Subscribe to an issue

> 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.

<div class="g1t-endpoint"><span class="g1t-method" data-method="put">PUT</span><code>/repos/{owner}/{name}/issues/{number}/subscription</code></div>

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.

- **Authentication:** Required. Send an [access token](/reference/api/#authentication) as `Authorization: Bearer`.
- **MCP tool:** [`notifications`](/reference/mcp/#notifications) with `action` `subscribe`, and the same inputs
- **Scope:** An access token needs [`notifications:write`](/guides/authentication/#scopes).
- **Also at:** [`PUT /notifications/threads/{id}/subscription`](/reference/api/notifications/set-thread-subscription/)

## Path parameters

| Name | Type | Required | Description |
| --- | --- | --- | --- |
| `owner` | string | Yes | The workspace that owns the repository. |
| `name` | string | Yes | The repository's name. |
| `number` | integer | Yes | With repo: the issue or pull request's number. |

## Body parameters

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

| Name | Type | Required | Description |
| --- | --- | --- | --- |
| `id` | string | No | A thread's id, from [`list_notifications`](/reference/api/notifications/list-notifications/). Or give repo and 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

```sh
curl -X PUT https://api.g1t.sh/repos/flagon-io/hello/issues/14/subscription \
  -H "Authorization: Bearer $G1T_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "subscribed": true
  }'
```

## Example response

A successful request answers `200` with:

```json
{
  "subscribed": true,
  "ignored": false,
  "reason": "manual",
  "repo": null,
  "number": 14,
  "updated_at": "2026-10-07T10:05: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](/reference/api/#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. |