# GitHub Issue Comments API

> List the comments on a GitHub issue or pull request by its URL, oldest first, with each commenter's login, their relationship to the repository, reactions and the comment text.

Source: https://www.sandbase.ai/apis/github/issue-comments
API reference: https://www.sandbase.ai/apis/github/issue-comments#api

## Facts

- Provider: GitHub
- Type: Data API
- Endpoint: `POST https://api.sandbase.ai/v1/api/github/issue-comments`
- 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/issue-comments` with `Authorization: Bearer $SANDBASE_API_KEY` and the parameters as a JSON body.

| Parameter | Type | Required | Allowed values |
| --- | --- | --- | --- |
| `url` | string | yes |  |
| `limit` | integer | no |  |
| `since` | string | no |  |
| `cursor` | string | no |  |
| `requireFields` | array | no |  |

## FAQ

### How do I use the GitHub Issue Comments API?

Send a POST request to https://api.sandbase.ai/v1/api/github/issue-comments 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 Issue Comments 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 Issue Comments API accept?

Required: url (string). Optional: limit (integer), since (string), cursor (string) and requireFields (array). The Parameters table and the Playground on this page list every field.

### What does the GitHub Issue Comments API return?

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

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

No. GitHub Issue Comments 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 Issue Comments API

List the comments on a GitHub issue or pull request by its URL, oldest first, with each commenter's login, their relationship to the repository, reactions and the comment text.

#### 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/issue-comments", "url": "https://github.com/openai/whisper/pull/1838", "limit": 10}'
```

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 | URL of a GitHub issue or pull request, e.g. https://github.com/openai/whisper/pull/1838. |
| `cursor` | string | No | Pagination cursor from a previous response's nextCursor. |
| `limit` | integer | No | Rows per page, 1-100 (GitHub's own page-size limit). Each call returns one full page of this size; use nextCursor for the next page. Default `100`. |
| `requireFields` | array | No | Optional; omit it and routing is unchanged, with the cheapest source serving. Name the output fields this request must be able to return, for example `authorAssociation` or `body`, and it is served only by a source that  |
| `since` | string | No | Only comments last-active on or after this date (YYYY-MM-DD). |

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