Simulate Policy — POST /api/v1/release-gate-policies/simulate
Simulate Policy
Simulate a draft policy against a past run’s decision data.
Endpoint: POST /api/v1/release-gate-policies/simulate
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 Admin or higher.
Parameters
Section titled “Parameters”| Name | In | Required | Type | Default | Description |
|---|---|---|---|---|---|
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”| Content type | Body | Required |
|---|---|---|
application/json | PolicySimulateRequest | yes |
Responses
Section titled “Responses”| Status | Meaning | Body |
|---|---|---|
200 | Successful Response | PolicySimulateResponse (application/json) |
422 | Validation Error | HTTPValidationError (application/json) |
Errors this endpoint returns, read from its source code:
404, with messages such as “No release decision found for this run. Trigger deep investigation first”, “Test run not found”
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: Release Gate Policies
- Operation ID:
simulate_policy_api_v1_release_gate_policies_simulate_post - Source code:
backend/app/routers/release_gate_policies.py, line 504 - Specification: OpenAPI JSON