How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Need help?

Contact us
GitHub

GitHub Reactions API

The Reactions API from GitHub — 16 operation(s) for reactions.

Documentation Provider Profile APIs.io OpenAPI GitHub

GitHub Reactions API is one of 350 APIs that GitHub publishes on the APIs.io network, described by a machine-readable OpenAPI specification and an AsyncAPI event-driven specification.

Tagged areas include Reactions. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, an AsyncAPI specification, and an API reference.

This API exposes 25 operations across 16 paths, and defines 10 schemas. It is described by OpenAPI 3.2.0, at version 1.1.4.

Requests are made against 2 base URLs: {protocol}://{hostname}/api/v3, {protocol}://{hostname}.

25 operations 16 paths 10 schemas 7 DELETE9 GET9 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.1.4
Base URL
https://api.github.com
Authentication
HTTP Bearer
License
MIT
Terms of Service
View terms
Resource Areas
1

Authentication & Security 1

GitHub Reactions API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (bearerHttpAuthentication).

  • bearerHttpAuthentication — Bearer Token

Paths & Operations 25

Across 16 paths, the API surfaces 25 operations — 7 DELETE, 9 GET, 9 POST. Each is listed below with its method, path, parameters, and response codes.

Reactions 25

Interact with reactions to various GitHub entities.

GET
/orgs/{org}/teams/{team_slug}/discussions/{discussion_number}/comments/{comment_number}/reactions
GitHub List Reactions for a Team Discussion Comment
reactions/list-for-team-discussion-comment-in-org 7 params → 200
POST
/orgs/{org}/teams/{team_slug}/discussions/{discussion_number}/comments/{comment_number}/reactions
GitHub Create Reaction for a Team Discussion Comment
reactions/create-for-team-discussion-comment-in-org 4 params body → 200201
DELETE
/orgs/{org}/teams/{team_slug}/discussions/{discussion_number}/comments/{comment_number}/reactions/{reaction_id}
GitHub Delete Team Discussion Comment Reaction
reactions/delete-for-team-discussion-comment 5 params → 204
GET
/orgs/{org}/teams/{team_slug}/discussions/{discussion_number}/reactions
GitHub List Reactions for a Team Discussion
reactions/list-for-team-discussion-in-org 6 params → 200
POST
/orgs/{org}/teams/{team_slug}/discussions/{discussion_number}/reactions
GitHub Create Reaction for a Team Discussion
reactions/create-for-team-discussion-in-org 3 params body → 200201
DELETE
/orgs/{org}/teams/{team_slug}/discussions/{discussion_number}/reactions/{reaction_id}
GitHub Delete Team Discussion Reaction
reactions/delete-for-team-discussion 4 params → 204
GET
/repos/{owner}/{repo}/comments/{comment_id}/reactions
GitHub List Reactions for a Commit Comment
reactions/list-for-commit-comment 6 params → 200404
POST
/repos/{owner}/{repo}/comments/{comment_id}/reactions
GitHub Create Reaction for a Commit Comment
reactions/create-for-commit-comment 3 params body → 200201422
DELETE
/repos/{owner}/{repo}/comments/{comment_id}/reactions/{reaction_id}
GitHub Delete a Commit Comment Reaction
reactions/delete-for-commit-comment 4 params → 204
GET
/repos/{owner}/{repo}/issues/comments/{comment_id}/reactions
GitHub List Reactions for an Issue Comment
reactions/list-for-issue-comment 6 params → 200404
POST
/repos/{owner}/{repo}/issues/comments/{comment_id}/reactions
GitHub Create Reaction for an Issue Comment
reactions/create-for-issue-comment 3 params body → 200201422
DELETE
/repos/{owner}/{repo}/issues/comments/{comment_id}/reactions/{reaction_id}
GitHub Delete an Issue Comment Reaction
reactions/delete-for-issue-comment 4 params → 204
GET
/repos/{owner}/{repo}/issues/{issue_number}/reactions
GitHub List Reactions for an Issue
reactions/list-for-issue 6 params → 200404410
POST
/repos/{owner}/{repo}/issues/{issue_number}/reactions
GitHub Create Reaction for an Issue
reactions/create-for-issue 3 params body → 200201422
DELETE
/repos/{owner}/{repo}/issues/{issue_number}/reactions/{reaction_id}
GitHub Delete an Issue Reaction
reactions/delete-for-issue 4 params → 204
GET
/repos/{owner}/{repo}/pulls/comments/{comment_id}/reactions
GitHub List Reactions for a Pull Request Review Comment
reactions/list-for-pull-request-review-comment 6 params → 200404
POST
/repos/{owner}/{repo}/pulls/comments/{comment_id}/reactions
GitHub Create Reaction for a Pull Request Review Comment
reactions/create-for-pull-request-review-comment 3 params body → 200201422
DELETE
/repos/{owner}/{repo}/pulls/comments/{comment_id}/reactions/{reaction_id}
GitHub Delete a Pull Request Comment Reaction
reactions/delete-for-pull-request-comment 4 params → 204
GET
/repos/{owner}/{repo}/releases/{release_id}/reactions
GitHub List Reactions for a Release
reactions/list-for-release 6 params → 200404
POST
/repos/{owner}/{repo}/releases/{release_id}/reactions
GitHub Create Reaction for a Release
reactions/create-for-release 3 params body → 200201422
DELETE
/repos/{owner}/{repo}/releases/{release_id}/reactions/{reaction_id}
GitHub Delete a Release Reaction
reactions/delete-for-release 4 params → 204
GET
/teams/{team_id}/discussions/{discussion_number}/comments/{comment_number}/reactionsdeprecated
GitHub List Reactions for a Team Discussion Comment (Legacy)
reactions/list-for-team-discussion-comment-legacy 6 params → 200
POST
/teams/{team_id}/discussions/{discussion_number}/comments/{comment_number}/reactionsdeprecated
GitHub Create Reaction for a Team Discussion Comment (Legacy)
reactions/create-for-team-discussion-comment-legacy 3 params body → 201
GET
/teams/{team_id}/discussions/{discussion_number}/reactionsdeprecated
GitHub List Reactions for a Team Discussion (Legacy)
reactions/list-for-team-discussion-legacy 5 params → 200
POST
/teams/{team_id}/discussions/{discussion_number}/reactionsdeprecated
GitHub Create Reaction for a Team Discussion (Legacy)
reactions/create-for-team-discussion-legacy 2 params body → 201

Schemas 10

The contract defines 10 schemas that model the data the API accepts and returns. The most detailed are nullable-simple-user (21 properties), nullable-simple-user_3 (21 properties), nullable-simple-user_4 (21 properties), nullable-simple-user_2 (21 properties). Each schema is shown below with its type and property counts.

validation-error
object
Validation Error
3 properties 2 required
basic-error
object
Basic Error
4 properties
reaction
object
Reactions to conversations provide a way to help people express their feelings more simply and effectively.
5 properties 5 required
nullable-simple-user
objectnull
A GitHub user.
21 properties 18 required
nullable-simple-user_2
object
GitHub user.
21 properties 18 required
validation-error_2
object
Validation Error
3 properties 2 required
nullable-simple-user_3
object
GitHub user.
21 properties 18 required
validation-error_3
object
Validation Error
3 properties 2 required
nullable-simple-user_4
object
GitHub user.
21 properties 18 required
validation-error_4
object
Validation Error
3 properties 2 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

github-reactions-api-openapi.yml Raw ↑

Other APIs GitHub publishes across the network.

GitHub Events API
AE Profile APIs.io
GitHub Feeds API
AE Profile APIs.io
GitHub Gists API
AE Profile APIs.io
GitHub Issues API
AE Profile APIs.io
GitHub Licenses API
AE Profile APIs.io
GitHub Markdown API
AE Profile APIs.io
GitHub Meta API
AE Profile APIs.io
GitHub Notifications API
AE Profile APIs.io
GitHub Octocat API
AE Profile APIs.io
GitHub Projects API
AE Profile APIs.io
GitHub Repos API
AE Profile APIs.io
GitHub Search API
AE Profile APIs.io
#Reactions
← Back to G APIs
API Details
ID
github:github-reactions-api
Base URL
https://api.github.com
Docs
https://docs.github.com/en/rest/apps?apiVersion=2022-11-28
Provider
GitHub
APIs.io →  GitHub →
Explore more
All APIs Providers APIs.io Network
Work with this as data

Every API here is available over the API and to AI agents over MCP. APIs is not yet its own endpoint on the v1 API. Reach this content through network search and the tag graph, or the MCP server below.

Installs https://mcp.apievangelist.com/mcp in Claude, Cursor, VS Code and the rest — one button, every client.

MCP tools for apis
4 tools reach this content
  • search_api_evangelistSearch every content type across the network at once.
  • find_relatedThe shared-tag relevance graph — what else covers this.
  • get_tagEverything one tag labels, across all content types.
  • guide_topicPRO — a curated bundle for a topic: area, guidance, rules, papers, stories, services.
All tools & prompts
Call it yourself
curl for this page
Search the network for this 
curl "https://api.apievangelist.com/v1/search?q=github-reactions-api&limit=10"
Everything under a tag 
curl "https://api.apievangelist.com/v1/tags/github-reactions-api"

Discovery needs no key. Full bodies and the synthesis endpoints are Pro.

Get an API key

Free tier, no email required. Sign in with whichever identity you already have.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have. Your account

Where this information came from

This is an independent, third-party profile of GitHub Reactions API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.