POST /orgs/{org}/teams/{team_slug}/discussions/{discussion_number}/reactions
Create a reaction to a team discussion.
A response with an HTTP 200 status means that you already added the reaction type to this team discussion.
[!NOTE] You can also specify a team by
org_idandteam_idusing the routePOST /organizations/:org_id/team/:team_id/discussions/:discussion_number/reactions.
OAuth app tokens and personal access tokens (classic) need the write: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. |
org |
String | Yes |
The organization name. The name is not case sensitive. |
Request headers
| Name | Type | Required | Description |
|---|---|---|---|
Content-Type |
String | Yes |
The media type of the request body.
Default value: "application/json" |
Request body fields
| Name | Type | Required | Description |
|---|---|---|---|
content |
String | Yes |
The reaction type to add to the team discussion. 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.