Skip to main content

Run Scheduled Chat now

Admit an idempotent manual occurrence without moving the normal recurring cadence.

POST/api/scheduled/{schedule_id}/run-now
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.

Returns HTTP 202 with a queued occurrence. Admission is not completion. Follow its operationRunId and the owner-scoped run endpoint. Execution may consume credits and can require additional input or approval.

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.

  • idempotencyKeyrequired

    string

    8–200 character retry identity. Reuse it for the same manual occurrence.

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