# GitHub Repository Issues API

> List a GitHub repository's issues and pull requests by repository URL (GitHub lists pull requests as issues), with each one's author, state, labels, counts and body. Filter by state, sort and last-activity date.

Source: https://www.sandbase.ai/apis/github/repository-issues
API reference: https://www.sandbase.ai/apis/github/repository-issues#api

## Facts

- Provider: GitHub
- Type: Data API
- Endpoint: `POST https://api.sandbase.ai/v1/api/github/repository-issues`
- Price: From $0.0012 per call
- Capabilities: api, github, developer, code
- Billing: pay per use from one SandBase balance; no provider account or subscription needed

## Call it

`POST https://api.sandbase.ai/v1/api/github/repository-issues` with `Authorization: Bearer $SANDBASE_API_KEY` and the parameters as a JSON body.

| Parameter | Type | Required | Allowed values |
| --- | --- | --- | --- |
| `url` | string | yes |  |
| `page` | integer | no |  |
| `sort` | string | no | created, updated, comments |
| `limit` | integer | no |  |
| `order` | string | no | desc, asc |
| `since` | string | no |  |
| `state` | string | no | open, closed, all |

## FAQ

### How do I use the GitHub Repository Issues API?

Send a POST request to https://api.sandbase.ai/v1/api/github/repository-issues with your SandBase API key in the Authorization header (Bearer) and the parameters as a JSON body. You can also try it in the Playground on this page without writing code.

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

From $0.0012 per call, billed from your SandBase balance. You are only charged for calls you make; there is no subscription.

### What parameters does the GitHub Repository Issues API accept?

Required: url (string). Optional: page (integer), sort (one of created, updated, comments), limit (integer), order (one of desc, asc), since (string) and state (one of open, closed, all). The Parameters table and the Playground on this page list every field.

### What does the GitHub Repository Issues API return?

A JSON response returned in the same HTTP request (synchronous).

### Do I need a GitHub developer account or API key?

No. GitHub Repository Issues runs through SandBase, so one SandBase API key covers this endpoint and every other API and model in the catalog. You do not need to apply for GitHub API access separately.

## README

### GitHub Repository Issues API

List a GitHub repository's issues and pull requests by repository URL (GitHub lists pull requests as issues), with each one's author, state, labels, counts and body. Filter by state, sort and last-activity date.

#### Request

```bash
curl -X POST "https://api.sandbase.ai/v1/run" \
  -H "Authorization: Bearer $SANDBASE_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"model": "github/repository-issues", "url": "https://github.com/openai/whisper"}'
```

The result is returned in `outputs[0].data`. Lookups that find nothing fail with a not-found error.

#### Parameters

| Name | Type | Required | Description |
|---|---|---|---|
| `url` | string | Yes | GitHub repository URL, e.g. https://github.com/openai/whisper. |
| `limit` | integer | No | Rows per page, 1-100 (GitHub's own page-size limit). Keep it the same while walking pages, because it sets the page size. Default `100`. |
| `order` | string | No | Sort direction. Defaults to desc. One of: `desc`, `asc`. |
| `page` | integer | No | 1-based page of issues. Request page + 1 while hasMore is true. Default `1`. |
| `since` | string | No | Only issues last-active on or after this date (YYYY-MM-DD). |
| `sort` | string | No | Sort by creation date, last update, or number of comments. Defaults to opened. One of: `created`, `updated`, `comments`. |
| `state` | string | No | Which issues to list. Defaults to open. One of: `open`, `closed`, `all`. |

#### Pricing

Billed at the actual cost of each call, about $0.0012 per request. A call can cost more when the first data source fails and another one answers. Failed calls and lookups that find nothing are not charged.
