Flaky Readiness — GET /api/v1/metrics/flaky-readiness
Flaky Readiness
Does this project have enough history to score flakiness at all?
Endpoint: GET /api/v1/metrics/flaky-readiness
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 |
|---|---|---|---|---|---|
project_id | query | yes | string | Project to measure — readiness is never a fleet average | |
days | query | no | integer | 90 | |
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 | Not documented (application/json) |
422 | Validation Error | HTTPValidationError (application/json) |
Response fields not documented. The API specification does not describe the body of every response this endpoint returns, so this page cannot list those fields. The body is not empty. To see it, call the endpoint on your own installation. All endpoints with undocumented responses.
Errors this endpoint returns, read from its source code:
422, with the message “project_id must be a UUID”
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: Metrics
- Operation ID:
flaky_readiness_api_v1_metrics_flaky_readiness_get - Source code:
backend/app/routers/metrics.py, line 165 - Specification: OpenAPI JSON