findings

Acknowledge, mark a fix applied, or dismiss

The human half of the lifecycle. fix_applied captures a baseline of the affected prompts server-side and starts the recheck clock: fourteen days later a recheck cycle measures again, and the finding becomes resolved only if the movement gates pass — a significant change whose 95% interval excludes zero, and at least five points of change — else not_moved, with the verdict's outcome saying which kind. Neither resolved nor not_moved can be set by a request.

Structural findings — a refused AI crawler, content that needs JavaScript, a page never crawled — are confirmed from first-party data instead: they need no prompt baseline, recheck is null, and the finding becomes resolved as soon as the fix shows up in the logs or on the page.

post/findings/{findingId}/transition

Request

  • Base URL: https://shruwd.io/api/v1
  • URL: https://shruwd.io/api/v1/findings/{findingId}/transition
  • Auth: HTTP bearer

Request body

to'acknowledged' | 'fix_applied' | 'dismissed' required

fix_applied starts the recheck clock. resolved/not_moved are decided by the recheck.

notestring

Response

Moved.

findingIdstring required
numberinteger required
fromstring required
tostring required
baselineCapturedboolean required

Changes

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