Trigger Deep Investigation — POST /api/v1/deep-investigate/{run_id}

Trigger Deep Investigation

Trigger the deep investigation pipeline for a completed test run. Uses workflow_type=“deep” which adds failure clustering, flaky sentinel, test health analysis, and release risk on top of the standard 5-stage pipeline.

Endpoint: POST /api/v1/deep-investigate/{run_id}

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 test run.

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

Content type	Body	Required
application/json	TriggerDeepRequest	yes

Responses

Status	Meaning	Body
200	Successful Response	TriggerDeepResponse (application/json)
422	Validation Error	HTTPValidationError (application/json)

Errors this endpoint returns, read from its source code:

• 404, with the message “Test run not found”
• 422
• 500

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

• Group: Deep Investigation
• Operation ID: trigger_deep_investigation_api_v1_deep_investigate__run_id__post
• Source code: backend/app/routers/deep_investigation.py, line 119
• Specification: OpenAPI JSON