GITHUB API

GitHub Discussion Search API

Search GitHub Discussions by keyword and filter by repository, author, comment count, date or whether they are answered. Each result includes the title, category, author, comment count and answered status.

Endpoint
POST /github/search-discussions
Price
1 credit per request
SDK
client.github.searchDiscussions()
MCP tool
github_search_discussions
Terminal
curl -X POST "https://api.bridgly.app/github/search-discussions" \
-H "Authorization: Bearer $BRIDGLY_KEY" \
-H "Content-Type: application/json" \
-d '{
"query": "feature request",
"answered": false,
"count": 10
}'
[ REQUEST AND RESPONSE ]

What does the GitHub Discussion Search API return?

GitHub discussions API: search GitHub Discussions by keyword, repo, author, comment count, dates and answered status, with category and comment count. Every response has the same envelope: the result in data, plus timeMs and the creditsCost of the call.

Request body

querystring
Free-text search terms, matched against the default fields for this search type, e.g. "web framework".
ownersstring[]
Limit to these owners (users or orgs). Maps to `user:`.
reposstring[]
Limit to these "owner/name" repositories. Maps to `repo:`.
authorstring
Opened by this user. Maps to `author:`.
commentsobject
Filter by comment count. Provide any of gt / gte / lt / lte; combine a lower and upper bound for a range.
comments.gtnumber · nullable
Strictly greater than this value.
comments.gtenumber · nullable
Greater than or equal to this value.
comments.ltnumber · nullable
Strictly less than this value.
comments.ltenumber · nullable
Less than or equal to this value.
createdobject
Filter by creation date. Provide any of gt / gte / lt / lte as YYYY-MM-DD dates; combine a lower and upper bound for a range.
created.gtstring · nullable
Strictly after this date (YYYY-MM-DD).
created.gtestring · nullable
On or after this date (YYYY-MM-DD).
created.ltstring · nullable
Strictly before this date (YYYY-MM-DD).
created.ltestring · nullable
On or before this date (YYYY-MM-DD).
updatedobject
Filter by last update date. Provide any of gt / gte / lt / lte as YYYY-MM-DD dates; combine a lower and upper bound for a range.
updated.gtstring · nullable
Strictly after this date (YYYY-MM-DD).
updated.gtestring · nullable
On or after this date (YYYY-MM-DD).
updated.ltstring · nullable
Strictly before this date (YYYY-MM-DD).
updated.ltestring · nullable
On or before this date (YYYY-MM-DD).
answeredboolean
Whether the discussion is answered. Maps to `is:answered`.
orderenum · default desc
Sort direction. Defaults to "desc".
desc | asc
countinteger · 1–10 · default 10
Number of results to return (1–10). Defaults to 10.
cursorstring
The previous response's `nextCursor`, to fetch the next page. Omit it for the first page.

Example response

200 OK · application/json
{
"timeMs": 1840,
"creditsCost": 1,
"data": {
"nextCursor": "string",
"query": "string",
"totalCount": 0,
"discussions": [
{
"id": "string",
"number": 0,
"title": "string",
"url": "string",
"authorLogin": "string",
"category": "string",
"repository": "string",
"repositoryUrl": "string",
"commentsCount": 0,
"isAnswered": true,
"createdAt": "string",
"updatedAt": "string"
}
]
}
}
[ USE CASES ]

What can you build with the GitHub Discussion Search API?

Find unanswered questions

List open, unanswered discussions about your product.

Collect feature requests

Gather ideas posted in discussions across your repositories.

Build a FAQ

Turn the most-commented answered discussions into help articles.

[ FAQ ]

GitHub Discussion Search API questions

How do I find unanswered questions in GitHub Discussions?

Set answered to false and add repos or owners to limit it to a project. Each discussion has its title, category, author, comment count and answered status.

Can I use GitHub Discussions for product research?

Yes. Discussions hold the questions and ideas users raise about a project. Searching them for a feature or pain point shows how often it comes up.

How do I get more than 10 results from a GitHub discussion search?

Each call returns up to 10 discussions and a nextCursor. Send it back as cursor to get the next page; it is null when there are no more.

How do I use the GitHub Discussion Search API?

Send a POST request to https://api.bridgly.app/github/search-discussions with the filters you want in the JSON body and your API key in the Authorization header. In the TypeScript SDK, call client.github.searchDiscussions(). AI agents connected to Bridgly over MCP can call the github_search_discussions tool.

How much does the GitHub Discussion Search API cost?

Costs 1 credit per request. Credits cost $2.00 per 1,000 on pay-as-you-go and as low as $1.00 per 1,000 at volume. New accounts on a business email start with 100 free credits, and failed requests are never charged.

Try the GitHub Discussion Search API

100 free credits on business email, no card. Your first call takes a minute.

APIMCPSDKCLI
free credits

On business email signup. No credit card required.

Start free with 100 credits