Update Review Gate — PUT /api/v1/settings/review-gate
Update Review Gate
Set the enforcement date (an ISO-8601 instant with an offset; past or future) or clear it with null (back to audit only). A past instant enforces at once. Interactive login only; audited once per actual change.
Endpoint: PUT /api/v1/settings/review-gate
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 | ReviewGateWrite | yes |
Responses
Section titled “Responses”| Status | Meaning | Body |
|---|---|---|
200 | Successful Response | ReviewGateRead (application/json) |
422 | Validation Error | HTTPValidationError (application/json) |
Errors this endpoint returns, read from its source code:
422, with the message “enforced_from is out of range”
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: Settings
- Operation ID:
update_review_gate_api_v1_settings_review_gate_put - Source code:
backend/app/routers/app_settings.py, line 1797 - Specification: OpenAPI JSON