What people said about this run, oldest first
const url = 'https://beta-api.plune.ai/v1/runs/2489E9AD-2EE2-8E00-8EC9-32D5F69181C0/comments';const options = {method: 'GET', headers: {Authorization: 'Bearer <token>'}};
try { const response = await fetch(url, options); const data = await response.json(); console.log(data);} catch (error) { console.error(error);}curl --request GET \ --url https://beta-api.plune.ai/v1/runs/2489E9AD-2EE2-8E00-8EC9-32D5F69181C0/comments \ --header 'Authorization: Bearer <token>'M6 (#1256). The live comments on a run, 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 run 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 ”Header Parameters
Section titled “Header Parameters ”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 ”The comments
object
The live ones, oldest first.
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
Example
{ "comments": [ { "id": "6f1c2b3a-0000-4000-8000-0000000000a4", "authorId": "6f1c2b3a-0000-4000-8000-0000000000a2", "body": "Step 3 is stale since the checkout redesign — the coupon field moved into the order summary.", "createdAt": "2026-09-18T10:12:00.000Z" } ]}No / invalid token or session
No such run in this project, or it is in the bin
object
Example
{ "error": "run '6f1c2b3a-0000-4000-8000-0000000000d1' not found"}