Update a guardrail
PATCH/v1/projects/:project_id/guardrails/:guardrail_id
Updates an existing guardrail. A document write that actually changes the policy increments version and archives the new document as a GuardrailVersion; metadata-only edits (name / description / context), and re-writing the document the guardrail already holds, leave the version untouched.
Request
Responses
- 200
- 400
- 401
- 403
- 404
- 409
- 413
- 429
- 500
- 502
- 4XX
Guardrail updated
Bad Request — invalid document or variable reference
Unauthorized
Forbidden
Not found
The resource has moved past the version this write read (VERSION_CONFLICT): a stated expected_version or If-Match no longer matches, or a concurrent write took the version first. meta.current_version names the version in force. Nothing is written.
REQUEST_REJECTED — the request body is over the size the body parser accepts
QUOTA_EXCEEDED — a requests quota on the calling API key or its project is spent for the window; Retry-After says when it reopens
Response Headers
Seconds until the quota window admits a request again
Unexpected server error — INTERNAL_ERROR, with the raw message never forwarded
The deployment's admission service is asked about this write and did not answer — ADMISSION_UNAVAILABLE; the write did not happen
The deployment's admission service refused this write — answered under the service's own 4xx status, with its code (matching ^[A-Za-z_][A-Za-z0-9_]{0,63}$, not necessarily an ERROR_CODES key), message and meta; the write did not happen. A status this operation also declares on its own is documented there