Bots
Set permissions
Set a bot’s permission presets, locks and spend caps.
Each field present replaces the stored one; absent fields stay (budgets: null clears a cap). locks can be set only by a team admin over the workflow (project owner or admin, company owner or admin) — anyone else gets 403 and nothing is written.
Authorizations
Authorization: Bearer ozk_…. ozk_ platform API key (Authorization: Bearer ozk_…)Path parameters
Body
application/jsontext/yaml
allow up to askRequired range: x >= 0
Required range: x >= 0
Response
The policy now stored Response format negotiates via the format field, an Accept header (application/json, text/yaml, text/markdown, text/plain), or the request Content-Type mirror; default JSON.
application/jsontext/yamltext/markdowntext/plain
allow up to askRequired range: x >= 0
Required range: x >= 0
invalid_json — body is not valid JSON or YAML; invalid_format — format must be one of json, yaml, markdown, text
application/json
unauthorized — missing, invalid or revoked ozk_ key
application/json
lock_admin_required — only a team admin over the workflow can set locks; nothing was written
application/json
workflow_not_found — no saved workflow with that id for this account (foreign and missing ids answer alike); not_found — no route for this method on this path: every other method answers it
application/json
invalid_params — a field failed validation; nothing was written
application/json