Run Failure Signatures — GET /api/v1/runs/failure-signatures
Run Failure Signatures
The top failure signatures of each failed build, for grouping them by error.
Endpoint: GET /api/v1/runs/failure-signatures
Authentication: Send a signed-in user’s access token in Authorization: Bearer <access token>, or an API key in X-API-Key: <API key>.
Parameters
Section titled “Parameters”| Name | In | Required | Type | Default | Description |
|---|---|---|---|---|---|
run_id | query | yes | array of string (uuid) | Repeatable: 1-50 run ids. | |
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 | RunSignatureBatchResponse (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: Test Runs
- Operation ID:
run_failure_signatures_api_v1_runs_failure_signatures_get - Source code:
backend/app/routers/runs.py, line 327 - Specification: OpenAPI JSON