Preview Schedule

POST /schedules/preview

What this spec would do, without doing it. Authors get cron wrong constantly and a preview is cheaper than a support conversation (§2.7).

Role floor

Requires viewer or above. The floor is a minimum, not a grant: scope filtering still applies on top of it, and a resource in another tenant answers 404 rather than 403.

Request body — SchedulePreviewRequest

Field	Type		Notes
kind	cron | interval | one_shot | event	required	—
cron_expressions	string[]	optional	—
timezone	string	optional	Default "UTC". max length 60
interval_seconds	integer | null	optional	min 60
fire_at	string (date-time) | null	optional	—
event_kind	string | null	optional	max length 60
count	integer	optional	Default 5. min 1 max 50

Responses

Status	Description	Body
200	Successful Response	SchedulePreview
422	Validation Error	HTTPValidationError

Only the success paths are declared

Any operation may also answer any status in the error catalogue, and every failure body is the platform envelope — including the 422 this document types as HTTPValidationError.

Example

The body shows the fields the schema always carries. Which combination is legal is a service rule the schema cannot express, so read the description above before copying this.

curl -X POST https://your-deployment.example.com/schedules/preview \
  -H "Authorization: Bearer $COBRE_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
       "kind": "cron"
     }'

Response — SchedulePreview

Field	Type		Notes
timezone	string	required	—
fires	PreviewFireView[]	required	—
warnings	string[]	required	—