GET /repos/{owner}/{repo}/issues

List issues in a repository. Only open issues will be listed.

[!NOTE] GitHub's REST API considers every pull request an issue, but not every issue is a pull request. For this reason, "Issues" endpoints may return both issues and pull requests in the response. You can identify pull requests by the pull_request key. Be aware that the id of a pull request returned from "Issues" endpoints will be an issue id. To find out the pull request id, use the "List pull requests" endpoint.

This endpoint supports the following custom media types. For more information, see "Media types."

application/vnd.github.raw+json: Returns the raw markdown body. Response will include body. This is the default if you do not pass any specific media type.
application/vnd.github.text+json: Returns a text only representation of the markdown body. Response will include body_text.
application/vnd.github.html+json: Returns HTML rendered from the body's markdown. Response will include body_html.
application/vnd.github.full+json: Returns raw, text, and HTML representations. Response will include body, body_text, and body_html.

Servers

https://api.github.com

Path parameters

Name	Type	Required	Description
`repo`	String	Yes	The name of the repository without the `.git` extension. The name is not case sensitive.
`owner`	String	Yes	The account owner of the repository. The name is not case sensitive.

Query parameters

Name	Type	Required	Description
`assignee`	String	No	Can be the name of a user. Pass in `none` for issues with no assigned user, and `*` for issues assigned to any user.
`page`	Integer	No	The page number of the results to fetch. For more information, see "Using pagination in the REST API." Default value: 1
`milestone`	String	No	If an `integer` is passed, it should refer to a milestone by its `number` field. If the string `*` is passed, issues with any milestone are accepted. If the string `none` is passed, issues without milestones are returned.
`labels`	String	No	A list of comma separated label names. Example: `bug,ui,@high`
`direction`	String	No	The direction to sort the results by. Possible values: `"desc"` `"asc"` Default value: "desc"
`sort`	String	No	What to sort results by. Possible values: `"updated"` `"created"` `"comments"` Default value: "created"
`per_page`	Integer	No	The number of results per page (max 100). For more information, see "Using pagination in the REST API." Default value: 30
`type`	String	No	Can be the name of an issue type. If the string `*` is passed, issues with any type are accepted. If the string `none` is passed, issues without type are returned.
`since`	String	No	Only show results that were last updated after the given time. This is a timestamp in ISO 8601 format: `YYYY-MM-DDTHH:MM:SSZ`.
`mentioned`	String	No	A user that's mentioned in the issue.
`state`	String	No	Indicates the state of the issues to return. Possible values: `"open"` `"closed"` `"all"` Default value: "open"
`creator`	String	No	The user that created the issue.

How to start integrating

Add HTTP Task to your workflow definition.
Search for the API you want to integrate with and click on the name.
- This loads the API reference documentation and prepares the Http request settings.
Click Test request to test run your request to the API and see the API's response.