---
title: "Mark an issue as resolved"
method: POST
path: "/api/v2/rescanAgent/markResolved"
tags: ["Rescan Agent"]
---

# Mark an issue as resolved

`POST /api/v2/rescanAgent/markResolved`

## Request

- Base URL: `https://zeropath.com`
- URL: `https://zeropath.com/api/v2/rescanAgent/markResolved`
- Auth: API key in header `X-ZeroPath-API-Token-Id` and API key in header `X-ZeroPath-API-Token-Secret`

Mark a vulnerability issue as resolved with a reason explaining why. The issue must be within the rescan agent's scope and must still be active (not already marked as no longer detected). The resolution is recorded and the full_scan worker handles the final lifecycle transition. Use this when the agent has verified that a previously reported vulnerability is no longer present in the code.

## Request body

- RescanAgentMarkResolvedRequest: Input for marking an issue as resolved. The agent provides a reason explaining why the issue is no longer present.
  - `issueId` string, uuid, required: UUID of the issue to mark as resolved.
  - `reason` string, required: Explanation of why the issue is resolved (e.g. "Fixed by commit abc123" or "False positive — input is already sanitized").

## Response `200`

Issue marked as resolved

- RescanAgentMarkResolvedResponse: Response confirming the issue was marked as resolved.
  - `issueId` string, required: UUID of the resolved issue.
  - `reason` string, required: The resolution reason provided.
  - `resolved` boolean, required: Always true on success.

## Other responses

- `401`: Error Response
- `404`: Error Response

---

[API](https://skmtc.dev/zeropath/apis/zeropath-api.md) - [All operations](https://skmtc.dev/zeropath/apis/zeropath-api/llms.txt) - [OpenAPI document](https://skmtc.dev/zeropath/apis/zeropath-api/revisions/126e9c80ba0d?raw)