Get organization discussion comment reply list¶

GET /api/v5/orgs/{org}/discuss/{number}/comment/{comment_id}/reply

This endpoint gets the reply list of a comment under a discussion in the specified organization. It returns details for each reply such as the author information, content and Markdown-formatted content, like count, and reply count, and supports paginated queries.

Access token support¶

AtomGit user access token (AtomGit user access tokens)

Anonymous access¶

This endpoint allows anonymous access

Request parameters¶

Parameter	Location	Type	Required	Description
`org`	path	string	Yes	Organization path
`number`	path	string	Yes	Discussion number
`comment_id`	path	string	Yes	Comment ID
`access_token`	query	string	No	User authorization code (anonymous access allowed; carry a token to access private organization discussions)
`page`	query	string	No	Current page number
`per_page`	query	string	No	Number of items per page, maximum 100, default 20

Response parameters¶

Field	Type	Always returned	Nullable	Description
`id`	string	Yes	No	Reply ID
`created_at`	string	Yes	No	Creation time
`author`	object	Yes	No	Reply author information
`content`	string	Yes	No	Reply content
`md_content`	string	Yes	No	Markdown format of the reply content
`is_hide`	integer	Yes	No	Whether hidden
`reply_total`	integer	Yes	No	Reply total
`like_total`	integer	Yes	No	Like total
`is_like`	boolean	Yes	No	Whether the current logged-in user has liked
`is_deleted`	integer	Yes	No	Whether deleted
`is_remark`	integer	Yes	No	Whether flagged (the exact meaning could not be determined)

Note: The response body is a JSON array, where each element represents a comment reply; the table above describes the fields of an array element.

author object

Field	Type	Always returned	Nullable	Description
`author.avatar_url`	string	Yes	No	Author avatar URL
`author.id`	string	Yes	No	Author ID
`author.object_id`	string	Yes	No	Author object ID
`author.login`	string	Yes	No	Author login name
`author.name`	string	Yes	No	Author name

Error response¶

This endpoint has no clearly parseable business failure response; error response fields follow what the backend actually returns.

HTTP response status codes¶

Status code	Description
`200`	Success (OK)
`401`	Authentication required (Requires authentication)
`403`	Access forbidden (Forbidden)
`404`	Resource not found (Not found)

Request example¶

Parameter description¶

replace <org> with the organization path (path); replace <number> with the discussion number; replace <comment_id> with the comment ID. This endpoint allows anonymous access, so the example sends no token by default; to access discussions of a private organization, append &access_token=<token> to the query string, where <token> is your AtomGit user access token.

cURL¶

curl -X GET 'https://api.atomgit.com/api/v5/orgs/<org>/discuss/<number>/comment/<comment_id>/reply?page=1&per_page=20' \
  -H 'Accept: application/json'

JavaScript¶

// Native fetch (Node.js 18+ / browser)
const response = await fetch(
  "https://api.atomgit.com/api/v5/orgs/<org>/discuss/<number>/comment/<comment_id>/reply?page=1&per_page=20",
  {
    headers: {
      "Accept": "application/json",
    },
  }
);

if (!response.ok) {
  throw new Error(`Request failed: ${response.status}`);
}

const data = await response.json();
console.log(data);

Python¶

import requests

resp = requests.get(
    "https://api.atomgit.com/api/v5/orgs/<org>/discuss/<number>/comment/<comment_id>/reply",
    params={"page": 1, "per_page": 20},
    headers={"Accept": "application/json"},
    timeout=10,
)
resp.raise_for_status()

print(resp.json())

Response example¶

Status code: 200

[
  {
    "id": "string",
    "created_at": "string",
    "author": {
      "avatar_url": "string",
      "id": "string",
      "object_id": "string",
      "login": "string",
      "name": "string"
    },
    "content": "string",
    "md_content": "string",
    "is_hide": 0,
    "reply_total": 0,
    "like_total": 0,
    "is_like": true,
    "is_deleted": 0,
    "is_remark": 0
  }
]

Error codes¶

Error code	Description
`401`	Unauthenticated or invalid credentials (missing/invalid access credentials)
`400`	Parameter error or unparsable request
`404`	Request path does not exist
`405`	Method not supported
`429`	Too many requests; rate limit triggered
`500`	Internal server error

Markdown source: View on AtomGit·Content from the open-source project gitcode-dev/atomgit-api-doc