GitHub Issue comments API
API health
- 24h health
- Normal
- 24h average time
- —
- Healthy / normal
- Available
- Limited
- Mostly down
Last 24 hours
Last 30 days
Read the comments on one GitHub issue or pull request in posting order, up to 100 per call, each with text, author, the author's relation to the repository, reactions and a direct link.
Price $0.96 per 1,000 requests ($0.000958 per call). Failed calls and empty results are not charged. Synchronous. For slow jobs add "mode": "async" to the body, take the job_id and poll.
AI prompt
Please help me write a data collection script with the EveryInfra GitHub Issue comments endpoint (github/issue_comments).
How the endpoint works:
- Request: POST https://api.everyinfra.com/api/v1/social with the header Authorization: Bearer <API key>. Read the key from the EVERYINFRA_API_KEY environment variable and never hard-code it.
- In the request body, set platform to github and action to issue_comments, and put the parameters inside params.
- Required parameters:
- url: A GitHub repository link such as https://github.com/facebook/react or just facebook/react; for issue_comments, the full link of an issue or pull request such as https://github.com/openai/whisper/pull/1838.
- Optional parameters:
- limit: The most rows to return in this call, an integer from 1 to 100. The default applies when you leave it out, and a call can return fewer rows. Larger values return 422 before any charge. (default: 30)
- Returns a list of records. Main fields of each record: id (GitHub's numeric ID, as a string), url, text, reaction_count (Total emoji reactions), author_username, author_id, author_avatar_url, author_type (Author account type: User, Bot or Organ…), author_association (The author's relation to the repository…), posted_at, updated_at (Last update time, ISO 8601 UTC), issue_url (The requested issue or pull request lin…).
- Example request body:
{
"platform": "github",
"action": "issue_comments",
"params": {
"url": "https://github.com/openai/whisper/pull/1838"
}
}
- Price: $0.96 per 1,000 requests; failed and empty results are not charged.
- For dozens or hundreds of targets, add "mode": "async" to the body: you get a job_id at once and poll GET https://api.everyinfra.com/api/v1/jobs/{job_id} for the result.
- On 422, fix the request using the suggested parameter names and allowed values in the error; on 429 or 503, wait for Retry-After and try again.
Before writing code, ask me which targets I need, how many, which fields, and what output format I want; then confirm the plan and the rough cost with me.Request parameters
| Name | In | Type | Required | Default | Description |
|---|---|---|---|---|---|
Authorization | header | string | Yes | - | Bearer followed by your API key. Create it in the console; never put it in a URL or a code repository. |
platform | body | string | Yes | github | Platform identifier, fixed value. |
action | body | string | Yes | issue_comments | Capability identifier, fixed value. |
url | body.params | string | Yes | - | A GitHub repository link such as https://github.com/facebook/react or just facebook/react; for issue_comments, the full link of an issue or pull request such as https://github.com/openai/whisper/pull/1838. Other formats are rejected before any charge. |
limit | body.params | integer (1–100) | No | 30 | The most rows to return in this call, an integer from 1 to 100. The default applies when you leave it out, and a call can return fewer rows. Larger values return 422 before any charge. |
Code samples
curl -X POST 'https://api.everyinfra.com/api/v1/social' \
-H "Authorization: Bearer $EVERYINFRA_API_KEY" \
-H 'Content-Type: application/json' \
--data-raw '{
"platform": "github",
"action": "issue_comments",
"params": {
"url": "https://github.com/openai/whisper/pull/1838"
}
}'OpenAPI definition (JSON)Samples read the key from the EVERYINFRA_API_KEY environment variable; copied code never contains your key.
Response example
No sample response is available for these parameters yet. This preview shows the response shape and fields from the API definition, with … as placeholders; it is not the result of a live call.
{
"id": "req_…",
"platform": "github",
"action": "issue_comments",
"results": [
{
"id": …,
"url": …,
"text": …,
"reaction_count": …,
"author_username": …,
"author_id": …,
"author_avatar_url": …,
"author_type": …,
"author_association": …,
"posted_at": …,
"updated_at": …,
"issue_url": …,
"platform": …
}
],
"count": …,
"billing": {
"charged": …,
"charged_usd": …,
"balance_after_usd": …,
…
},
"quota": { … }
}Response fields
Business data is in results. The table lists the fields a record can contain; values the platform does not show are never made up.
| Field | Meaning |
|---|---|
id | GitHub's numeric ID, as a string. |
url | Link to the record on the platform. |
text | Body text with HTML removed, returned in full and never cut short (on a few platforms the list results themselves carry only an excerpt; the platform's field notes say so). |
reaction_count | Total emoji reactions. |
author_username | Author's username (@handle), usually usable in URLs. |
author_id | Author's unique ID on the platform. |
author_avatar_url | Keeps the platform's own meaning |
author_type | Author account type: User, Bot or Organization. |
author_association | The author's relation to the repository, as GitHub reports it: OWNER, MEMBER, COLLABORATOR, CONTRIBUTOR, FIRST_TIME_CONTRIBUTOR, NONE and so on. |
posted_at | Publish time in ISO 8601, UTC (for example 2026-08-07T12:34:56+00:00). Non-standard strings from the platform are passed through as is, so parse defensively. null means the platform does not disclose it. |
updated_at | Last update time, ISO 8601 UTC. |
issue_url | The requested issue or pull request link (issue_comments). |
platform | Source platform identifier, the same as platform in the request (for example xiaohongshu, tiktok). |
Errors and billing
- 401
- Missing or invalid key.
- 402
- Insufficient balance. Top up first.
- 422
- Invalid parameter name or value. Fix it using the suggestions in the error. No charge.
- 429
- Per-minute request limit reached. Wait for Retry-After, then try again.
- 503
- Could not complete. The held charge is returned to your balance. If the outcome is unknown, verify it before you retry.
- 200 empty
- No data. No charge.
Official references
Used only to check objects and terms. They do not imply authorization or endorsement of EveryInfra by the platform.
- GitHub REST API: list issue comments ↗
GitHub's REST reference lists the comments of an issue by repository and number and notes that every pull request is also an issue, so both issues/<number> and pull/<number> links in `url` point to one conversation. Review comments on code lines are not part of it.
Checked 2026-11-01