Operations
Operations

Update settings

Update the agent's privacy and call settings in one call: recording and AI disclosure, PII scrubbing, call-data retention, telemetry content, call recording and whether it continues after a transfer (recordAfterTransfer), post-call analysis (which metrics run is set_metric_activation), the silence check-in, the timezone, phoneMatchLowRisk and the overflow number. Pass only the fields to change; null on a tri-state field inherits the workspace default. It clears readiness risks such as 'recording-disclosure-missing'. Call handling, answering hours, guardrails and the widget theme have their own tools: set_call_handling, set_answering_hours, set_safety_guardrails and set_widget_theme.

POST
/operations/update_agent_settings

Authorization

bearerAuth
AuthorizationBearer <token>

A personal access token from Settings > API tokens.

In: header

Header Parameters

Idempotency-Key?string

A key you choose, such as a UUID, that makes this POST safe to retry. Within 24 hours the same key and request answers with the first successful answer and runs nothing, the same key with a different request answers 422 idempotency_key_reused, and a key whose request is still running answers 409 idempotency_key_in_use. A failed request keeps nothing, so the same key runs it again.

Length1 <= length <= 255

Request Body

application/json

TypeScript Definitions

Use the request body type in TypeScript.

Response Body

application/json

application/problem+json

application/problem+json

application/problem+json

application/problem+json

application/problem+json

application/problem+json

application/problem+json

curl -X POST "https://example.com/operations/update_agent_settings" \  -H "Content-Type: application/json" \  -d '{    "agent": "string"  }'
{}
{
  "type": "http://example.com",
  "title": "string",
  "status": 0,
  "detail": "string",
  "code": "string",
  "errors": [
    {
      "path": "string",
      "message": "string"
    }
  ],
  "estimate": {},
  "retryAfterSeconds": 0
}
{
  "type": "http://example.com",
  "title": "string",
  "status": 0,
  "detail": "string",
  "code": "string",
  "errors": [
    {
      "path": "string",
      "message": "string"
    }
  ],
  "estimate": {},
  "retryAfterSeconds": 0
}
{
  "type": "http://example.com",
  "title": "string",
  "status": 0,
  "detail": "string",
  "code": "string",
  "errors": [
    {
      "path": "string",
      "message": "string"
    }
  ],
  "estimate": {},
  "retryAfterSeconds": 0
}
{
  "type": "http://example.com",
  "title": "string",
  "status": 0,
  "detail": "string",
  "code": "string",
  "errors": [
    {
      "path": "string",
      "message": "string"
    }
  ],
  "estimate": {},
  "retryAfterSeconds": 0
}
{
  "type": "http://example.com",
  "title": "string",
  "status": 0,
  "detail": "string",
  "code": "string",
  "errors": [
    {
      "path": "string",
      "message": "string"
    }
  ],
  "estimate": {},
  "retryAfterSeconds": 0
}
{
  "type": "http://example.com",
  "title": "string",
  "status": 0,
  "detail": "string",
  "code": "string",
  "errors": [
    {
      "path": "string",
      "message": "string"
    }
  ],
  "estimate": {},
  "retryAfterSeconds": 0
}
{
  "type": "http://example.com",
  "title": "string",
  "status": 0,
  "detail": "string",
  "code": "string",
  "errors": [
    {
      "path": "string",
      "message": "string"
    }
  ],
  "estimate": {},
  "retryAfterSeconds": 0
}

Undo the last change POST

Put the draft back the way it was before your last change to it, or before your last `steps` changes. Before each change you make to the draft, in the in-app Builder or assistant, over the MCP, through /v1 or with `vai push`, the server saves a checkpoint of the draft for you on this agent; it keeps your newest ten, and a Builder message counts as one change however many edits it made. This applies a checkpoint with apply_agent_spec replace: true, so it covers every field the spec covers, and returns `changedBack`, the steps it reversed in plain words, and `remaining`, how many more changes you can undo. Tell the user the changedBack list as it is. The checkpoints it went back past are used up, so calling it again goes back one change further. It refuses, changing nothing, when there is no checkpoint, when the checkpoints were saved on a version that is no longer this agent's draft (it was published or replaced since), or when the version is published. Changes made on the editor's own pages are not recorded, but an undo puts them back too when they came after the checkpoint.

Update alert POST

Edit an alert rule, the threshold-tuning workflow. Pause/resume with `enabled`, drop a noisy trend rule to sensitivityPreset 'conservative' (or raise minBreaches / windowCalls to debounce), re-bound a threshold rule (condition + thresholdValue/Low/High), change direction, or repoint the rule onto a different metric. Pass only the fields to change. Requires workspace-admin rights, same as creating an alert (delivery can reach Slack/email).