# Review a pull request

> Give a verdict on a pull request: approve it, or request changes and say what.

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

Read [`get_pull_request_changes`](/reference/api/pull-requests/get-pull-request-changes/) first. You cannot review a pull request you opened.

- **Authentication:** Required. Send an [access token](/reference/api/#authentication) as `Authorization: Bearer`.
- **MCP tool:** [`pull_request`](/reference/mcp/#pull_request) with `action` `review`, and the same inputs
- **Scope:** An access token needs [`pull_requests: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 |
| --- | --- | --- | --- |
| `verdict` | string | Yes | One of `approve`, `request_changes`. |
| `body` | string | No | Markdown. Required when requesting changes. |

## Example request

```sh
curl -X POST https://api.g1t.sh/repos/flagon-io/hello/pulls/14/reviews \
  -H "Authorization: Bearer $G1T_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "verdict": "request_changes",
    "body": "Trim the name before using it."
  }'
```

## Example response

A successful request answers `200` with:

```json
{
  "id": "cmt_01m43sx9f3h7k1n5r9v3z7d1g5",
  "kind": "comment",
  "author": {
    "id": "usr_01kz9d3f7h1k5n9r3v7z1c5g9b",
    "username": "ana",
    "kind": "user",
    "verified": true,
    "workspaces": [
      {
        "slug": "flagon-io",
        "role": "member"
      }
    ]
  },
  "body": "Trim the name before using it.",
  "path": null,
  "line": null,
  "verdict": "request_changes",
  "created_at": "2026-10-01T18:40:05.019Z"
}
```

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