source-tracker-admin

Edit the finding text before approval — the human voice the Findings section promises (v1.1 U5). Editing an APPROVED finding drops it back to PENDING: changed public prose must be re-vetted.

put/api/v1/admin/source-tracker/findings/{finding_id}

Request

  • Base URL: https://api.getanana.com (the document declares no server; this is the origin it was published from)
  • URL: https://api.getanana.com/api/v1/admin/source-tracker/findings/{finding_id}
  • Auth: none declared

Path parameters

finding_idstring uuid required

Request body

body_mdstring required

Response

Successful Response

finding_idstring uuid required
status'pending' | 'approved' | 'rejected' required

Lifecycle of a human-vetted "what changed" finding.

Deliberately 3 members (no INCOMPLETE): a finding is templated text a human approves or rejects — a "failed scan" state cannot occur on it.

Changes

    • info

      added the optional property // to the response with the status

    • info

      added the optional property // to the response with the status