List repositories with the GitHub API

Lists the repositories the account can reach: its own, those where it is a collaborator and those of its organizations. Each item has owner.login and name, which are the owner and repo the other tools ask for. Paginate with page and per_page: a page with fewer items than per_page is the last one.

Identifier
github_list_repositories

The request

POST https://connect.reportei.com/api/tools/github_list_repositories/execute
Authorization: Bearer <merchant token>
x-customer-token: <customer token>
Content-Type: application/json
Accept: application/json

{
  "customer_toolkit": "<connection UUID>",
  "arguments": {
    "visibility": "all"
  }
}

Your system sends your customer's connection id and the tool arguments. The headers are the same as the rest of the Connect API: your product's token and your customer's token.

Parameters

ParameterTypeRequiredDescription
visibilitystringNoOnly repositories with this visibility. The default is all.Values: all, public, private
affiliationstringNoComma-separated list of owner, collaborator and organization_member, to choose how the account relates to the repositories. The default is all three.
typestringNoOnly repositories of this type. Do not send it together with visibility or affiliation: the API answers 422.Values: all, owner, public, private, member
sortstringNoSort field. The default is full_name.Values: created, updated, pushed, full_name
directionstringNoSort order. The default is asc for full_name and desc for the others.Values: asc, desc
sincestringNoOnly repositories updated after this time, as YYYY-MM-DDTHH:MM:SSZ.
beforestringNoOnly repositories updated before this time, as YYYY-MM-DDTHH:MM:SSZ.
per_pageintegerNoResults per page, up to 100. The default is 30.
pageintegerNoPage number, starting at 1.

Supported connections

Your customer connects their GitHub account once, with one of the modes below. The same connection serves every tool of the toolkit.

API key

Your customer pastes the app's key on a Connect screen, or your system sends the key with POST /api/customer-toolkits, with no screen.

OAuth with your product's app

You register your product's OAuth app once, with POST /api/merchants/credentials/github, and your customer authorizes the account on a consent screen. Connect renews the token when it is about to expire.

The response

On success, Connect preserves the app's response status and body. HTTP errors returned by the app use the {error, api_error} envelope; authentication or validation can fail before execution. The X-Toolkit-Execution-Id header identifies the recorded execution, available at GET /api/tools/executions/{uuid}.

Ready for AI agents

This tool's input is a JSON Schema, available at GET /api/tools/github_list_repositories. It becomes your agent's tool definition with no conversion.

Other GitHub tools

See all 12 tools

Toolkits in the same category

See all 100 toolkits

See Connect applied to your product.

Try it for 15 days with no card, or walk our team through your use case.