---
title: "Add context to a pentest finding"
method: PUT
path: "/v1/pentest-finding-contexts/{issueId}"
tags: ["Security Penetration Tests"]
---

# Add context to a pentest finding

`PUT /v1/pentest-finding-contexts/{issueId}`

Saves a customer context note on a pentest finding, e.g. an accepted-by-design rationale or remediation details. Future scans of the same target pass the note to the testing agent so the issue is retested with that context.

## Path parameters

- `issueId` string, required

## Headers

- `X-Organization-Id` string

## Request body

- UpsertFindingContextDto
  - `runId` string, required — Penetration test run ID the finding belongs to
  - `context` string, required — Context for the finding, e.g. an accepted-by-design rationale or remediation details. Shared with the testing agent on future scans of the same target. Max 2000 characters.

## Response `200`

Context note saved

## Other responses

- `404` — Run or finding not found

---

[API](https://skmtc.net/trycompai/apis/comp-ai-api.md) · [All operations](https://skmtc.net/trycompai/apis/comp-ai-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/trycompai/comp-ai-api/versions/726b9523fb22/schema)