Skip to content
Plune Plune Plune Docs

What people said about this bug, oldest first

GET
/v1/bugs/{id}/comments
 
curl --request GET \
  --url https://beta-api.plune.ai/v1/bugs/2489E9AD-2EE2-8E00-8EC9-32D5F69181C0/comments \
  --header 'Authorization: Bearer <token>'

The live comments on a bug, the same shape and rules as a case’s: anyone in the project reads them, a reader too; the author is a userId to be named from GET /v1/members. A bug in the Bin, in another project or never there answers the same 404.

Authorizations

Section titled “Authorizations ”

Parameters

Section titled “ Parameters ”

Path Parameters

Section titled “Path Parameters ”
id
required
string format: uuid

Header Parameters

Section titled “Header Parameters ”
X-Plune-Project
string

Which of your projects to act in — an id from GET /v1/projects. Absent, your default project. A project you are not a member of answers 404, the same as one that does not exist. Ignored under a bearer token, which is bound to the project it was minted in.

Responses

Section titled “ Responses ”

200

Section titled “200 ”

The comments

Media type application/json
object
comments
required

The live ones, oldest first.

Array<object>

What somebody said about a case (B8-team T5): plain text with its line breaks, no Markdown, no edit — a changed mind is a second comment. The author is a userId; the dashboard names them from GET /v1/members.

object
id
required
string format: uuid
authorId
required
string
body
required
string
<= 8192 characters
createdAt
required
string format: date-time
Example 
{
  "comments": [
    {
      "id": "6f1c2b3a-0000-4000-8000-0000000000a4",
      "authorId": "6f1c2b3a-0000-4000-8000-0000000000a2",
      "body": "Reproduced on staging as well.",
      "createdAt": "2026-09-18T10:12:00.000Z"
    }
  ]
}

401

Section titled “401 ”

No / invalid token or session

404

Section titled “404 ”

No such bug in this project

Media type application/json
object
error
required
string
Example generated
{
  "error": "example"
}