Post a comment on a finding
POST/api/v1/findings/:finding_id/comments
Post a comment (optionally a reply, optionally with @mentions).
@mentioned org members are validated and notified. A reply must target a top-level comment on the SAME finding (single-level threading).
- Scope required:
findings:read— per the dev spec, any org member who can read the finding may comment (triage is a conversation, not a manager-only action). Edit/delete are author-or-admin (see below).
Request
Responses
- 200
- 400
- 401
- 403
- 404
- 409
- 422
- 429
- 500
Successful Response
Bad request — malformed input or failed validation.
Missing, expired, or invalid credentials.
Authenticated but not authorized for this resource. Note: cross-organization reads return 404, not 403.
Resource not found, or hidden for tenant-enumeration safety (the caller lacks permission to know whether the resource exists).
Conflict — the current resource state does not allow this operation (e.g. assessment already started, email already in use).
Semantic validation failure — request shape was valid but contents were not.
Too many requests — rate limited. Retry after the window resets.
Internal server error — unexpected failure.