urlstringrequired
GitHub repository URL, e.g. https://github.com/openai/whisper.
GitHub Repository Issues
https://api.sandbase.ai/v1/api/github/repository-issuesList 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.
- Price
- From $0.0012USD / call
- Method
- POST
- Response
- JSON
- Parameters
- 1 required · 6 optional
Playground
Input
GitHub repository URL, e.g. https://github.com/openai/whisper.
1-based page of issues. Request page + 1 while hasMore is true. Minimum: 1.
Sort by creation date, last update, or number of comments. Defaults to opened.
1100
Rows per page, 1-100 (GitHub's own page-size limit). Keep it the same while walking pages, because it sets the page size. Range: 1 to 100.
Sort direction. Defaults to desc.
Only issues last-active on or after this date (YYYY-MM-DD).
Which issues to list. Defaults to open.
OutputReady
Your output will appear here
Complete the inputs, then click Run.
API 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
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.
Start building
Send your first request
Platform API endpoint with unified authentication and usage tracking.
# The quoted heredoc keeps Unicode and shell metacharacters unchanged.
result=$(curl --fail-with-body --silent \
-X POST "https://api.sandbase.ai/v1/api/github/repository-issues" \
-H "Authorization: Bearer $SANDBASE_API_KEY" \
-H "Content-Type: application/json" \
--data-binary @- <<'SANDBASE_JSON'
{
"url": "https://github.com/openai/whisper",
"page": 1,
"limit": 100
}
SANDBASE_JSON
)
printf '%s\n' "$result"2. Authentication
Set your SandBase API key in your server environment. Requests use Bearer authentication.
export SANDBASE_API_KEY="YOUR_API_KEY"Keep your key on the server. Do not expose it in browser code.
3. Parameters
pageinteger
1-based page of issues. Request page + 1 while hasMore is true.
Default: 1
sortstring
Sort by creation date, last update, or number of comments. Defaults to opened.
Possible values: created, updated, comments
limitinteger
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
orderstring
Sort direction. Defaults to desc.
Possible values: desc, asc
sincestring
Only issues last-active on or after this date (YYYY-MM-DD).
statestring
Which issues to list. Defaults to open.
Possible values: open, closed, all
4. Response
Saved example response for this API; no live request is made when viewing it.
No saved response has been published. Run the API in Playground to inspect its response.
Explore more
Related APIs
| API | Price | Response |
|---|---|---|
GitHub Repository IssuesThis API GitHub | From $0.0012 per call | JSON |
GitHub | From $0.0012 per call | JSON |
GitHub | From $0.0012 per call | JSON |
GitHub | From $0.0012 per call | JSON |
GitHub | From $0.0012 per call | JSON |
GitHub | From $0.0012 per call | JSON |
Questions
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.