# GitHub Repo Issues API (https://www.socialcrawl.dev/platforms/github/repo-issues)

> Returns issues for the repository under `data.items[]`. NOTE: GitHub treats pull requests as issues for this endpoint: every PR also appears here, distinguishable by the presence of a `pull_request` field on the item. Filter by `state`, comma-separated `labels`, sort by `created`/`updated`/`comments`, and paginate with `per_page`/`page`. `since` accepts an ISO 8601 timestamp.

TL;DR: `GET /v1/github/repo/issues` costs 1 credit per call and returns SocialCrawl's unified JSON schema. Single x-api-key auth, 100 free credits on signup.

## Parameters

| Parameter | Required | Description |
| --- | --- | --- |
| `url` | yes | GitHub repo URL: `https://github.com/{owner}/{repo}`. |
| `type` | no | Filter the unified issues+PRs list: `issue` returns only issues, `pr` returns only pull requests, `all` (default) returns both. Each item also carries `post.ext.type` (`issue`/`pull_request`). (issue \| pr \| all) |
| `state` | no | `open`, `closed`, or `all`. Defaults to `open`. (open \| closed \| all) |
| `labels` | no | Comma-separated label names (e.g. `bug,help wanted`). |
| `sort` | no | `created`, `updated`, or `comments`. Defaults to `created`. (created \| updated \| comments) |
| `direction` | no | `asc` or `desc`. Defaults to `desc`. (asc \| desc) |
| `since` | no | Only issues updated at or after this ISO 8601 timestamp. |
| `per_page` | no | Issues per page (1-100). Defaults to 30. |
| `page` | no | 1-indexed page number. |
| `max_pages` | no | 1 to 50 (default 1, or 50 when `max_items` or `max_credits` is sent). Walk up to this many pages in one call and return the rows from all of them. Each page walked is billed exactly as one call to this endpoint (a cached page is free) and counts against your rate limit; its charge and any refund are recorded under the page's own request id, listed in `data.walk.request_ids`. The walk stops early at the last page, or when the request's time budget runs low; `data.walk.stopped` says why (`end`, `max_pages`, `max_items`, `max_credits`, `time_budget`, `page_error`) and `pagination.next_cursor` continues from where it stopped. |
| `max_items` | no | 1 to 5000. Get more in one call: keep walking pages until the response holds at least this many rows, then stop with `data.walk.stopped: "max_items"`. The last page is returned whole (it was billed), so `data.items` can hold up to one page more than this, and `pagination.next_cursor` resumes right after it without skipping a row. Walks up to 50 pages unless `max_pages` says fewer; each page is billed as one call (a cached page is free). Add `max_credits` to cap the spend. A long walk can stop on the time budget first (`"time_budget"`): send the returned cursor with the same params to continue. |
| `max_credits` | no | 1 to 100000. The most this call may spend, across every page it walks. A page starts only while the credits already spent plus that page's price (or, when higher, the most any page of this walk has cost) still fit, so the call never goes past it; the walk then stops with `data.walk.stopped: "max_credits"` and the cursor to resume. Sent alone, it walks as far as the budget goes (up to 50 pages). A value below the price of one page is a free 400 whose `error.details.page_credits` names that price. Credits a row join (`include=`) adds are known only once a page has run, so page 1 is checked against its own price. |

## Code example

```bash
curl -G "https://www.socialcrawl.dev/v1/github/repo/issues" \
  --data-urlencode "url=https://github.com/facebook/react" \
  -H "x-api-key: sc_YOUR_API_KEY"
```

## FAQ

### How do I list a repo's issues with an API?

Send a GET request to /v1/github/repo/issues with the repository URL in the url parameter. SocialCrawl returns issues and pull requests with title, number, state, author, label list, comment count, and creation and update timestamps.

### Does this return pull requests too, or just issues?

Both. GitHub treats pull requests as a kind of issue, so this endpoint returns both. Each item carries a flag indicating whether it is a PR, so you can split them out or keep them together depending on your use case.

### What filters can I apply to the issue list?

Filter state by open, closed, or all; pass a comma-separated labels list to narrow by label; and use since (an ISO timestamp) to fetch only issues updated after a point in time. Sort and pagination parameters are supported too.

### How do I paginate through a long issue list?

Use per_page to set the page size and page to walk forward, incrementing page until the array is short or empty. SocialCrawl handles GitHub's Link-header pagination behind that simple page number for you.

### How much does the GitHub Issues API cost?

Each list request costs 1 credit on the standard tier, regardless of how many issues come back on the page. New accounts get 100 free credits with no credit card required. For an AI summary of the issues, use the repo top-issues endpoint.

See the full GitHub API: https://www.socialcrawl.dev/platforms/github

## Pricing

- Standard endpoints: 1 credit per call
- Advanced endpoints: 5 credits per call
- Premium endpoints: 10 credits per call
- 100 free credits on signup, no credit card required. Cached responses cost 0 credits. Credit packs never expire.
- Full pricing: https://www.socialcrawl.dev/pricing

## Explore with AI

Questions this API answers, phrased for an AI assistant:

- How to list issues and pull requests for a repo with an API
- What does the SocialCrawl GitHub Issues API return?