Developer tools
GitHub in your product and your AI agents, through one API
The GitHub toolkit covers repositories, issues, issue comments and pull requests: list and search, create and update issues, comment, open a pull request and merge it. A customer connects with an API key or OAuth, and your product or AI agent calls every operation through one Connect endpoint, with the audit log of each execution kept by Connect.
15 days to try it. No credit card.
POST https://connect.reportei.com/api/tools/github_create_issue/execute
Authorization: Bearer <merchant token>
x-customer-token: <customer token>
Content-Type: application/json
Accept: application/json
{
"customer_toolkit": "<connection UUID>",
"arguments": {
"owner": "<owner>",
"repo": "<repo>",
"title": "<title>"
}
}How it works
From a connected customer to the first GitHub call.
- 1
Your customer connects the account
Your system opens a Connect session for the toolkit and your customer connects their GitHub account. You get the connection id.
- 2
Your product calls the tool
A POST to /api/tools/{tool}/execute with the connection id and arguments. On success, Connect preserves the app's response status and body.
- 3
Connect handles the rest
It stores the credential encrypted, renews tokens for OAuth connections that support renewal and records executions in an audit trail available through the API.
Use cases
What your product does with GitHub.
Bug reports become issues
When a user reports a problem in your product, create an issue in the right repository with title, body, labels and assignees.
Release tooling for teams
List open pull requests, read mergeable and mergeable_state, and merge the ones that are ready from your own release dashboard.
AI agent for code review flow
Let an agent search issues, read a pull request, comment on it and open a new pull request from a branch.
Tools
12 GitHub tools
- List repositoriesGETLists 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.
- Search issuesGETSearches issues and pull requests in every repository the account can see, with the GitHub search syntax in q. Returns total_count and items, up to 1,000 results per search; paginate with page and per_page. Each item has number, and repository_url ends with the owner and repo of the item.
- List issuesGETLists the issues of a repository, newest first. Pull requests come in the list too, marked with a pull_request key. Paginate with page and per_page: a page with fewer items than per_page is the last one.
- Get issueGETReturns an issue, with title, body, state, labels, assignees and milestone. An issue moved to another repository answers 301 with its new location.
- Create issuePOSTCreates an issue in a repository and returns it, with its number. Labels, assignees, milestone and type are silently dropped when the account has no push access to the repository. Notifies the watchers of the repository.
- Update issuePATCHChanges an issue and returns it. Only the fields sent change. To close it, send state closed with a state_reason. Labels and assignees replace the current ones, and an empty list clears them.
- List issue commentsGETLists the comments of an issue or of a pull request, oldest first. The review comments on the code of a pull request are not included. Paginate with page and per_page: a page with fewer items than per_page is the last one.
- Create issue commentPOSTAdds a comment to an issue or to a pull request and returns it. Notifies the participants.
- List pull requestsGETLists the pull requests of a repository, newest first. Paginate with page and per_page: a page with fewer items than per_page is the last one.
- Get pull requestGETReturns a pull request, with its branches, head.sha, mergeable and mergeable_state, the number of commits and changed files, and whether it was merged. mergeable may come null while GitHub computes it: call again after a few seconds.
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.
Questions about the GitHub toolkit
Do I need to build against the GitHub API?
No. Connect ships 12 GitHub tools, described and ready. Your customer connects the account and your system calls every tool through the same endpoint, with the same request format.
How does my customer connect their GitHub account?
With the mode the toolkit accepts: API key, OAuth with your product's app. Connect stores the credential encrypted and never returns it to your system.
Does it work with AI agents?
Yes. Each tool's input is described in JSON Schema, which your agent uses directly as a tool definition. The agent picks the tool and the arguments, and your system makes the call to Connect.
Does my customer need a Reportei account?
No. Your customer connects the account on a Connect screen, or your system sends the credential through the API, and they keep using only your product.
Toolkits in the same category
See all 100 toolkitsSee Connect applied to your product.
Try it for 15 days with no card, or walk our team through your use case.
