Skip to main content

Create Scheduled Chat

Create a draft recurring Command Center instruction; activate it separately to enable unattended work.

POST/api/scheduled
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.

Returns HTTP 201 and a draft definition. Creating a definition does not activate it. The host derives per-occurrence execution capacity and runtime operation scope; do not send operation allowlists or an authored execution budget. Activation is a separate request. See Scheduled Chat lifecycle and access.

Body parameters

  • namerequired

    string

    Non-empty display name, at most 160 characters.

  • promptrequired

    string

    Complete recurring instruction, at most 50,000 characters.

  • recurrencerequired

    object

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

  • executionMode · optional

    string

    Only new_thread is supported; every occurrence starts a fresh Command Center task.

  • resourceRefs · optional

    array

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

  • standingApprovalGrantId · optional

    string | null

    Optional existing standing grant identity; caller-supplied identity alone does not grant authority.

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