querystringrequired
GitHub issue search query with any of GitHub's qualifiers, e.g. "repo:openai/whisper is:pr", "is:issue label:bug author:octocat", "repo:ggml-org/llama.cpp is:pr is:merged opened:>2026-01-01".
GitHub Issue and PR Search
https://api.sandbase.ai/v1/api/github/search-issuesSearch issues and pull requests across GitHub with GitHub's own search syntax (repo:, is:pr, is:issue, author:, label:, opened:...), with each result's author, state, labels, counts and body. Use it to find who opens issues and pull requests on a repository.
- Price
- From $0.0024USD / call
- Method
- POST
- Response
- JSON
- Parameters
- 1 required · 4 optional
Playground
Input
GitHub issue search query with any of GitHub's qualifiers, e.g. "repo:openai/whisper is:pr", "is:issue label:bug author:octocat", "repo:ggml-org/llama.cpp is:pr is:merged opened:>2026-01-01".
1-based page of results. Request page + 1 while hasMore is true. Minimum: 1.
Sort by number of comments, creation date, last update, or reactions. Omit for best match.
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 when sort is set. Defaults to desc.
OutputReady
Your output will appear here
Complete the inputs, then click Run.
API README
GitHub Issue and PR Search API
Search issues and pull requests across GitHub with GitHub's own search syntax (repo:, is:pr, is:issue, author:, label:, opened:...), with each result's author, state, labels, counts and body. Use it to find who opens issues and pull requests on a repository.
Request
curl -X POST "https://api.sandbase.ai/v1/run" \
-H "Authorization: Bearer $SANDBASE_API_KEY" \
-H "Content-Type: application/json" \
-d '{"model": "github/search-issues", "query": "repo:openai/whisper is:pr"}'
The result is returned in outputs[0].data. Lookups that find nothing fail with a not-found error.
Parameters
| Name | Type | Required | Description |
|---|---|---|---|
query | string | Yes | GitHub issue search query with any of GitHub's qualifiers, e.g. "repo:openai/whisper is:pr", "is:issue label:bug author:octocat", "repo:ggml-org/llama.cpp is:pr is:merged opened:>2026-01-01". |
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 when sort is set. Defaults to desc. One of: desc, asc. |
page | integer | No | 1-based page of results. Request page + 1 while hasMore is true. Default 1. |
sort | string | No | Sort by number of comments, creation date, last update, or reactions. Omit for best match. One of: comments, created, updated, reactions. |
Pricing
Billed at the actual cost of each call, about $0.0024 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/search-issues" \
-H "Authorization: Bearer $SANDBASE_API_KEY" \
-H "Content-Type: application/json" \
--data-binary @- <<'SANDBASE_JSON'
{
"page": 1,
"limit": 100,
"query": "repo:openai/whisper is:pr"
}
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 results. Request page + 1 while hasMore is true.
Default: 1
sortstring
Sort by number of comments, creation date, last update, or reactions. Omit for best match.
Possible values: comments, created, updated, reactions
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 when sort is set. Defaults to desc.
Possible values: desc, asc
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 Issue and PR SearchThis API GitHub | From $0.0024 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 Issue and PR Search API?
Send a POST request to https://api.sandbase.ai/v1/api/github/search-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 Issue and PR Search API cost?
From $0.0024 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 and PR Search API accept?
Required: query (string). Optional: page (integer), sort (one of comments, created, updated, reactions), limit (integer) and order (one of desc, asc). The Parameters table and the Playground on this page list every field.
What does the GitHub Issue and PR Search 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 and PR Search 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.