Schedules
Update a schedule
Change a schedule.
Any of name, description, schedule (a cron — a schedule cannot become @once), timezone, status (active or paused), parameters (replaces the stored object; parameters.deliver is a list of {channel, chat_id?, to?} (a bare channel string is widened) with channel one of inapp, email, slack, telegram, whatsapp, discord, teams.) and ends_at (null clears it).
Authorizations
Authorization: Bearer ozk_…. ozk_ platform API key (Authorization: Bearer ozk_…)Path parameters
Body
application/jsontext/yaml
Available options: active, paused
Available options: json, yaml, markdown, text
Response
The changed schedule Response format negotiates via the format field, an Accept header (application/json, text/yaml, text/markdown, text/plain), or the request Content-Type mirror; default JSON.
application/jsontext/yamltext/markdowntext/plain
invalid_json / invalid_yaml / invalid_body — unreadable body; invalid_format — format must be one of json, yaml, markdown, text; invalid_request — the scheduler refused the change (the message says which)
application/json
unauthorized — missing, invalid or revoked ozk_ key
application/json
schedule_not_found — no schedule with that id for this key (a foreign, missing or deleted id answers alike); not_found — no route for this method on this path: every other method answers it
application/json
invalid_params — a field is missing or malformed (the envelope names it); nothing was written
application/json
scheduler_error — the scheduler failed or did not answer; no detail is returned, retry
application/json