Skip to main content

Update Scheduled Chat

Update definition fields and create an immutable revision using the current version.

PATCH/api/scheduled/{schedule_id}
HTTP referenceScope authenticated user session (developer API keys blocked)Updated October 15, 2026

This page documents the canonical HTTP contract for this endpoint.

Authenticate with the signed-in user session using a bearer token or the accessToken cookie. Developer API keys are blocked. Definitions, runs, and attention belong to the current user; current workspace membership is rechecked before accessing saved resources. Lists may include your own work across accessible workspaces.

Read the current version before a mutation and send it as expectedVersion. A stale version returns 409; read and reconcile before retrying. The HTTP contract requires this value even where Command Center binds it automatically.

Supply at least one definition field. Material edits create a new immutable revision. Review returned authority and authorityRefreshRequired; do not assume an edited definition has authority for unattended execution.

Path parameters

  • schedule_idrequired

    string

    Exact Scheduled Chat definition ID returned by create or list.

Body parameters

  • expectedVersionrequired

    integer

    Current schedule version, at least 1. Required for optimistic concurrency.

  • name · optional

    string

    Non-empty display name, at most 160 characters.

  • prompt · optional

    string

    Complete recurring instruction, at most 50,000 characters.

  • recurrence · optional

    object

    rrule and IANA timezone. Recurrence is validated by the host.

  • resourceRefs · optional

    array

    Up to 96 exact {type,id,metadata?} host-owned resources. Metadata supplies labels and does not authorize access.

Errors

StatusMeaning
401A valid signed-in user session is required.
403Developer API keys are blocked or workspace access is unavailable.
404The owner-scoped schedule, run, attention item, or referenced resource is unavailable.
409The version, status transition, authority, or active occurrence conflicts with this request.
422Invalid request fields, recurrence, or resource references.

Docs