Get Deep Findings — GET /api/v1/deep-investigate/{run_id}/findings
Get Deep Findings
Return deep investigation findings per failure cluster for a test run.
Endpoint: GET /api/v1/deep-investigate/{run_id}/findings
Authentication: Send a signed-in user’s access token in Authorization: Bearer <access token>, or an API key in X-API-Key: <API key>.
- You must have access to this test run.
Parameters
Section titled “Parameters”| Name | In | Required | Type | Default | Description |
|---|---|---|---|---|---|
run_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 |
|---|---|---|
200 | Successful Response | array of DeepFindingResponse (application/json) |
422 | Validation Error | HTTPValidationError (application/json) |
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: Deep Investigation
- Operation ID:
get_deep_findings_api_v1_deep_investigate__run_id__findings_get - Source code:
backend/app/routers/deep_investigation.py, line 334 - Specification: OpenAPI JSON