## github/repo/issues

`GET /v1/github/repo/issues`

List a repository's issues (pull requests included, flagged per item).

*GitHub repository issues*

| Parameter | Required | Description |
| --- | --- | --- |
| `url` | yes | Repository URL — e.g. `https://github.com/vercel/next.js` |
| `state` | no | Issue state: open, closed or all (default open) — e.g. `open` |
| `labels` | no | Comma-separated label names to filter by — e.g. `bug` |
| `type` | no | Client-side filter: issue or pr (GitHub's feed mixes both) — e.g. `issue` |
| `sort` | no | Sort key: created, updated or comments — e.g. `created` |
| `direction` | no | Sort direction: asc or desc — e.g. `desc` |
| `since` | no | Only items 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/repo/issues?url=https%3A%2F%2Fgithub.com%2Fvercel%2Fnext.js" \
  -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": 44,
      "number": 7,
      "title": "Example issue",
      "is_pull_request": false
    }
  ],
  "cursor": null,
  "has_more": null
}
```

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