Findings - Detail Remediation
AI-assisted remediation, pull requests and issues for a finding.
📄️ Generate Issue
Start the issue-generation flow for the finding identified by finding_id. Asynchronous: responds 202 with the PlexiFlow `run_id`; follow the run with `GET /automations/runs?finding_id=...&automation_id=...` until it is terminal. A COMPLETED run has written the issue remediation the finding page opens. Requires the generate-issue scope; responds 409 when the finding is pending false-positive review.
📄️ Generate AI Remediation
Request asynchronous AI remediation generation for a single finding. The request is accepted with 202 and the finding's Remediate flow (PlexiFlow) starts; the response carries its `run_id`. Responds 409 when the finding is pending false-positive review.
📄️ Get Remediation
Return the most recent remediation generated for the finding given by the finding_id query parameter. Responds 404 when no remediation exists and 422 when the finding ID is missing or not a valid ObjectId; access to the finding is checked before returning data.
📄️ Edit Remediation
Update editable fields of a remediation: diff, code_diff, and status. Any other field in the payload is rejected with 403 to prevent mass-assignment of server-managed data.
📄️ Delete Remediation
Discard a remediation so a bad generation can be thrown away and retried (discard-and-retry). Findings this remediation had parked in 'ready' are reverted to 'enriched' so they can be spent by a new generation; findings in any other status are left untouched. Responds 409 while a generation is still in flight, 403 for another tenant's remediation, 404 when it does not exist and 400 for a malformed ID. The delete is permanent — no un-delete is offered; recovery is a new generation.
📄️ Create Pull Request
Execute the PullRequest workflow that opens a pull request on the connected SCM for the remediation referenced in the request body.
📄️ Create Issue on SCM
Trigger the CreateIssue workflow to open an issue on the connected SCM provider (GitHub, GitLab, Bitbucket or Gitea) for a finding remediation. Requires a Bearer token with the create-issue scope.