CreateScheduleRequest

POST /v1/schedules. The client mints the stable schedule identity and supplies only reusable intent. The worker stamps owner, revision, lifecycle, creation time, and revision-effective time.

Type object

Shape

Field	Type	Description
schedulerequired	ScheduleId
workspacerequired	WorkspaceId
namerequired	ScheduleName	A person-authored schedule label. It is presentation metadata, never schedule identity, and is redacted anywhere a derived `Debug` can reach.
templaterequired	DelegationTemplate	The reusable request fields. `RunId`, executing device, and document version pins exist only for one claimed firing and cannot be stored here.
recurrencerequired	RecurrenceRule	A persisted recurrence rule. The variants preserve Koru's existing floating-versus-zoned distinction without an optional timezone.

Example

{
  "schedule": "00000000-0000-4000-8000-000000000000",
  "workspace": "00000000-0000-4000-8000-000000000000",
  "name": "string",
  "template": {
    "requested_by": {
      "profile": "00000000-0000-4000-8000-000000000000",
      "kind": "person"
    },
    "objective": "string",
    "agent": {
      "kind": "built_in",
      "value": "string"
    },
    "requested_model": "string",
    "scope": {
      "kind": "none"
    },
    "grants": [],
    "context": []
  },
  "recurrence": {
    "cron": "string",
    "type": "floating"
  }
}

The contract has no example values, so example bodies are generated from each schema: every field is shown with a placeholder of its type.

Used by

POST/v1/schedules
Create repeating delegated work

Generated from contract version 1. Last updated November 12, 2026.