Get Release Decision — GET /api/v1/release-readiness/{run_id}

Get Release Decision

Retrieve the release readiness decision with full council context: dimension scores, linked cluster insights, baseline diff, open defects, and override audit trail.

Endpoint: GET /api/v1/release-readiness/{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>.

• You must have access to this test run.

Parameters

Name	In	Required	Type	Default	Description
run_id	path	yes	string (uuid)
allow_advisory	query	no	boolean	false	While the review gate is enforced, return ADVISORY_<value> for an unreviewed AI decision instead of PENDING_REVIEW.
X-API-Key	header	no	string or null		API key, as an alternative to the access token (see Authentication).

Request body

No request body.

Responses

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

Errors this endpoint returns, read from its source code:

• 403, with the message “Advisory release values require the QA Lead role”
• 404, with the message “No release decision found. Trigger deep investigation first”

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: Release Readiness
• Operation ID: get_release_decision_api_v1_release_readiness__run_id__get
• Source code: backend/app/routers/release_readiness.py, line 46
• Specification: OpenAPI JSON