Update schedule
Edit a scheduled eval run, or pause/resume it. Sending `enabled` alone is the fast toggle (pausing a schedule is a first-class operator action, resuming recomputes the next run from now, never from a stale queue key). Any other field, name, cronExpression (5-field), timezone (IANA), numRuns, evalIds, re-validates the schedule and recomputes the next run server-side. Pass only the fields to change; the rest keep their current values.
Authorization
bearerAuth A personal access token from Settings > API tokens.
In: header
Header Parameters
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.
1 <= length <= 255Request 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_cron_job" \ -H "Content-Type: application/json" \ -d '{ "cronJobId": "string", "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
}Update call alert POST
Update ANY call alert by id, a built-in reason alert (new_lead/urgent/missed/message_taken/booking/all_calls) or a free-form custom one. For a built-in row, name/description can still be edited, but its reason itself can never change and it can never be deleted, use `enabled: false` to turn it off (or set its recipient array(s), emailAddresses, smsNumbers, slackChannelIds, to an empty list to stop it firing on just that channel without disabling the whole alert). Every field besides `id` is optional; pass only what changed. Same {{variable}} token vocabulary as create_call_alert. SCOPE: this op moves the agent scope only when you ask it to. Send `agentIds` to replace the list, or `allAgents: true` to widen it to the whole workspace. Editing any other field leaves the scope untouched. That is the opposite of create_call_alert, which scopes a new alert to the agent you addressed.
Update dashboard POST
Edit an Overview dashboard's chrome: rename it, change the default time range its widgets resolve against (Grafana-style 'now-7d' → 'now'), re-scope the agent multi-select, or toggle daily-report inclusion. Pass only the fields to change. Widgets are separate, add with add_dashboard_plot, remove with delete_dashboard_widget.