Updates an existing schedule. All fields in the request body are required - this is a full update. The schedule must belong to the authenticated user’s organization.
Documentation Index
Fetch the complete documentation index at: https://docs.emergence.ai/llms.txt
Use this file to discover all available pages before exploring further.
Bearer authentication header of the form Bearer <token>, where <token> is your auth token.
ID of the schedule to update
Request body for updating a schedule.
Unique human readable name for the schedule
Cron-based schedule configuration.
The cron expression is interpreted in the specified timezone. It will be converted to UTC for storage and execution.
Reference ID (e.g. workflow config ID) held in Data Readiness resources
Schedule configuration (currently only NOTIFICATION is supported)
Whether the schedule is ready to be triggered
Successful Response
Response body for a schedule.
Schedule values are returned in their original timezone for user-friendly display.
ID of the schedule
Unique human readable name for the schedule
Cron-based schedule response with timezone-aware values.
The cron expression is dynamically converted from UTC back to the original timezone specified by the user for display purposes.
Reference ID (e.g. workflow config ID) held in Data Readiness resources
Schedule configuration (currently only NOTIFICATION is supported)
Whether the schedule is ready to be triggered