Fetch existing AI analysis for a test case (no re-run) — GET /api/v1/analyze/{test_case_id}
Fetch existing AI analysis for a test case (no re-run)
Return the previously stored AI analysis for a test case without triggering a new LLM run. Returns 404 if no analysis has been run yet.
Endpoint: GET /api/v1/analyze/{test_case_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>.
- A minimum role applies. The source code names it.
Parameters
Section titled “Parameters”| Name | In | Required | Type | Default | Description |
|---|---|---|---|---|---|
test_case_id | path | yes | string | ||
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 | AnalysisResponse (application/json) |
422 | Validation Error | HTTPValidationError (application/json) |
Errors this endpoint returns, read from its source code:
404, with the message “No analysis found for this test case”422, with the message “Invalid test_case_id format”
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: AI Analysis
- Operation ID:
get_existing_analysis_api_v1_analyze__test_case_id__get - Source code:
backend/app/routers/analyze.py, line 160 - Specification: OpenAPI JSON