# React with an emoji

> React to an issue or a pull request with an emoji: to its description, or with comment_id to one of its comments. content is one of +1, -1, laugh, hooray, confused, heart, rocket and eyes; remove true takes your reaction back.

<div class="g1t-endpoint"><span class="g1t-method" data-method="post">POST</span><code>/repos/{owner}/{name}/issues/{number}/reactions</code></div>

Anyone who can read the repository may. Answers with the reactions it has now, each with its count and the usernames of who reacted (`g1t` for g1t, which reacts eyes to what it was asked to take on). [`get_issue`](/reference/api/issues/get-issue/) and [`get_pull_request`](/reference/api/pull-requests/get-pull-request/) give each comment's reactions, and the description's as reactions.

Reacting twice the same way is one reaction. Without comment_id it reacts to the issue's or pull request's description.

- **Authentication:** Required. Send an [access token](/reference/api/#authentication) as `Authorization: Bearer`.
- **MCP tool:** [`issue`](/reference/mcp/#issue) with `action` `react`, and the same inputs
- **Scope:** An access token needs [`issues:write`](/guides/authentication/#scopes).

## 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 | The number shown after the #. Issues and pull requests share one sequence. |

## Body parameters

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

| Name | Type | Required | Description |
| --- | --- | --- | --- |
| `content` | string | Yes | One of `+1`, `-1`, `laugh`, `hooray`, `confused`, `heart`, `rocket`, `eyes`. |
| `comment_id` | string | No | A comment on it, to react to that comment rather than to its description. |
| `remove` | boolean | No | Take your reaction back. |

## Example request

```sh
curl -X POST https://api.g1t.sh/repos/flagon-io/hello/issues/12/reactions \
  -H "Authorization: Bearer $G1T_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "content": "+1"
  }'
```

## Example response

A successful request answers `200` with:

```json
[
  {
    "content": "heart",
    "count": 1,
    "users": [
      "ana"
    ]
  },
  {
    "content": "eyes",
    "count": 1,
    "users": [
      "g1t"
    ]
  }
]
```

## 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 a token without the scope it needs. |
| 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. |