Schedules
Wake a schedule
Wake the schedule’s workflow once.
Fires the schedule’s saved workflow once through a one-time job (the scheduler’s runAgain), without touching the schedule itself. A pending wake is re-timed, never stacked. in delays it (seconds, or "10m"); the default is the scheduler’s next tick. note becomes the run’s input. job_id is the one-time job, next_run_at its ms epoch fire time.
Authorizations
Authorization: Bearer ozk_…. ozk_ platform API key (Authorization: Bearer ozk_…)Path parameters
Body
application/jsontext/yaml
Available options: json, yaml, markdown, text
Response
The wake-up 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
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); workflow_not_found — the schedule’s workflow is gone; 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; also a schedule that has no saved workflow (a heartbeat)
application/json
scheduler_error — the scheduler failed or did not answer; no detail is returned, retry
application/json