Update issue with the GitHub API
Changes 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.
- Identifier
- github_update_issue
The request
POST https://connect.reportei.com/api/tools/github_update_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>",
"issue_number": 1
}
}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
| Parameter | Type | Required | Description |
|---|---|---|---|
| owner | string | Yes | Login of the user or organization that owns the repository, the owner.login of List repositories. |
| repo | string | Yes | Name of the repository, the name of List repositories. |
| issue_number | integer | Yes | Number of the issue, the number of List issues or Search issues. |
| title | string | No | New title. |
| body | string | No | New content, in Markdown. |
| state | string | No | Closes or reopens the issue.Values: open, closed |
| state_reason | string | No | Why the state changed. Ignored unless state changes.Values: completed, not_planned, duplicate, reopened |
| duplicate_issue_id | integer | No | With state_reason duplicate, the id (not the number) of the issue this one duplicates, from the id field of List issues or Get issue. |
| labels | array | No | Names of the labels the issue should have, replacing the current ones. An empty list removes all. |
| assignees | array | No | Logins of the users the issue should be assigned to, replacing the current ones. An empty list removes all. |
| milestone | integer | No | Number of a milestone of the repository, from the milestone.number of an issue in List issues. |
| type | string | No | Name of an issue type of the organization, such as Bug or Task. |
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_update_issue. It becomes your agent's tool definition with no conversion.
Other 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.
- 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.
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.
