findings

Change a finding's status

Change the status of a finding.

Available to organizations and machine callers; the transition is validated and authorized by the finding status-change service, and noted in the finding's Updates thread.

Args: finding_id (int): Primary key of the finding. body (UpdateFindingStatusRequest): Requested status transition. db (AsyncSession): Request-scoped database session. context (ActiveContext): Resolved caller identity and scope.

Returns: UpdateFindingStatusResponse: The finding with its new status.

post/v1/findings/{finding_id}/status

Request

  • Base URL
    https://api.ethiack.com (the document declares no server; this is the origin it was published from)
  • Auth
    none declared

Path parameters

finding_idinteger required

Request body

status'draft' | 'open' | 'triaged' | 'invalid' | 'fixed' | 'duplicate' | 'accepted' required

Finding lifecycle status.

DRAFT is the author-private pre-submission state: a hacker (or machine) composes the finding as a draft, then submit advances it to OPEN / TRIAGED, at which point it becomes visible to the event's other members. Drafts are only ever seen by their author (and privileged actors).

Response

Successful Response

resultstring
finding_idstring required

Finding ID as hex string

Changes

No recorded changes to this operation across all 1 revision of this API.