Cancel Investigation — POST /api/v1/investigations/{investigation_id}/cancel
Cancel Investigation
Request cooperative cancellation (QA_ENGINEER+). The workflow checks the flag between nodes and finalizes the row as cancelled.
Endpoint: POST /api/v1/investigations/{investigation_id}/cancel
Authentication: Send a signed-in user’s access token in Authorization: Bearer <access token>, or an API key in X-API-Key: <API key>.
- Your role must be QA engineer or higher.
- You must have access to this investigation.
Parameters
Section titled “Parameters”| Name | In | Required | Type | Default | Description |
|---|---|---|---|---|---|
investigation_id | path | yes | string (uuid) | ||
X-API-Key | header | no | string or null | API key, as an alternative to the access token (see Authentication). |
Request body
Section titled “Request body”No request body.
Responses
Section titled “Responses”| Status | Meaning | Body |
|---|---|---|
202 | Successful Response | object (application/json) |
422 | Validation Error | HTTPValidationError (application/json) |
Errors this endpoint returns, read from its source code:
404, with the message “Investigation not found”409
It can also return 401 if your credential is missing or expired, 403 if your credential does not allow this request, and 404 if the item does not exist or you cannot see it. Your role, your project membership and the key’s scope decide what a credential allows. See Errors and retries.
More details
Section titled “More details”- Group: Agent Investigations
- Operation ID:
cancel_investigation_api_v1_investigations__investigation_id__cancel_post - Source code:
backend/app/routers/agent_investigations.py, line 254 - Specification: OpenAPI JSON