Configuration
Update guardrails
Credential: user token · Role: owner or admin (manage_team)
The same gate the Settings screens use — a viewer’s token cannot write a guardrail, decided by the same function.
Writes use strict schemas: unknown keys are rejected, not dropped.
PATCH
Update guardrails
Authorizations
A user token (pv_ut_…) as Authorization: Bearer pv_ut_…. X-Peeve-Key is accepted too. Never a query parameter — URLs end up in proxy logs and Referer headers.
The token carries its owner's live workspace role, re-read on every call.
Body
application/json
The body is of type object.
Update guardrails