## github/issue/comments

`GET /v1/github/issue/comments`

Comments on an issue or pull request, oldest first.

*GitHub issue comments*

| Parameter | Required | Description |
| --- | --- | --- |
| `url` | yes | Issue or pull request URL — e.g. `https://github.com/vercel/next.js/issues/1` |
| `since` | no | Only comments updated at or after this ISO-8601 timestamp — e.g. `2026-01-01T00:00:00Z` |
| `limit` | no | Items per page, max 100 — e.g. `25` |
| `cursor` | no | Opaque page cursor from a previous response — e.g. `2` |
| `dry_run` | no | Read a zero-credit estimate without fetching sources, running AI, or reserving credits. Cache status is a snapshot, not a guarantee at execution. — e.g. `1` |

**Cost:** 1 credit at list price per successful uncached response; variable-cost operations may quote or settle a different charge. Confirmed uncharged or refunded failures report zero. Pending reconciliation can report credits_used:null; retain request_id and the original idempotency key.

```bash
curl "https://www.monocrawl.com/v1/github/issue/comments?url=https%3A%2F%2Fgithub.com%2Fvercel%2Fnext.js%2Fissues%2F1" \
  -H "x-api-key: mn_your_key_here"
```

### Response data

Illustrative abbreviated data; documented core fields are optional and may be null. Additional source fields are allowed.

```json
{
  "items": [
    {
      "id": 45,
      "author": "example",
      "body": "Illustrative comment",
      "reactions": 0
    }
  ],
  "cursor": null,
  "has_more": null
}
```

[Field reference](https://www.monocrawl.com/docs/endpoints/github/issue/comments#response) · [JSON Schema for response.data](https://www.monocrawl.com/schemas/github/issue/comments.json)