GET /orgs/{org}/teams/{team_slug}/discussions/{discussion_number}/comments/{comment_number}/reactions
List the reactions to a team discussion comment.
[!NOTE] You can also specify a team by
org_idandteam_idusing the routeGET /organizations/:org_id/team/:team_id/discussions/:discussion_number/comments/:comment_number/reactions.
OAuth app tokens and personal access tokens (classic) need the read:discussion scope to use this endpoint.
Servers
- https://api.github.com
Path parameters
| Name | Type | Required | Description |
|---|---|---|---|
discussion_number |
Integer | Yes |
The number that identifies the discussion. |
team_slug |
String | Yes |
The slug of the team name. |
comment_number |
Integer | Yes |
The number that identifies the comment. |
org |
String | Yes |
The organization name. The name is not case sensitive. |
Query parameters
| Name | Type | Required | Description |
|---|---|---|---|
page |
Integer | No |
The page number of the results to fetch. For more information, see "Using pagination in the REST API." Default value: 1 |
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 |
content |
String | No |
Returns a single reaction type. Omit this parameter to list all reactions to a team discussion comment. Possible values:
|
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.