Skip to main content
PUT
/
v1
/
pentest-finding-contexts
/
{issueId}
Add context to a pentest finding
curl --request PUT \
  --url https://api.trycomp.ai/v1/pentest-finding-contexts/{issueId} \
  --header 'Content-Type: application/json' \
  --header 'X-API-Key: <api-key>' \
  --data '
{
  "runId": "pentest-abc123",
  "context": "Read access to appConfiguration is accepted by design: the collection only holds non-secret bootstrap configuration and write access is restricted to privileged users."
}
'

Authorizations

​
X-API-Key
string
header
required

API key for authentication

Headers

​
X-Organization-Id
string

Organization ID (required for session auth, optional for API key auth)

Path Parameters

​
issueId
string
required

Body

application/json
​
runId
string
required

Penetration test run ID the finding belongs to

Example:

"pentest-abc123"

​
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.

Maximum string length: 2000
Example:

"Read access to appConfiguration is accepted by design: the collection only holds non-secret bootstrap configuration and write access is restricted to privileged users."

Response

Context note saved