Create a schedule
Creates a hand-authored schedule that syncs one action for one linked account. It is yours to change or delete, unlike a schedule fanned out from a sync config.
Authorizations
Basic authentication header of the form Basic <encoded-value>, where <encoded-value> is the base64-encoded string username:password.
Body
The linked account to sync.
"3fa85f64-5717-4562-b3fc-2c963f66afa6"
The action to sync. The account's connector profile must already have a sync config for it.
"hris_list_employees"
The parameters the action is called with on each run. Every parameter the action requires must be supplied; call GET /v2/data_sync/sync_configs/{id}/parameters to discover them.
A human-readable name for the schedule. Defaults to the action id.
Whether the schedule is active on creation.
How often the sync fires. ISO 8601 duration (e.g. PT1H); inherited from the sync config when omitted.
The point after which an incremental sync falls back to a full sync. ISO 8601 duration; inherited from the sync config when omitted.
When the schedule should first fire; null for no start time, omit to inherit it from the sync config.
Response
The schedule was created.
The unique identifier of the schedule.
The linked account this schedule syncs.
The action this schedule runs.
The human-readable name of the schedule.
The parameters the action is called with on each run.
A hash of sync_params, distinguishing schedules for the same action.
Whether the schedule is currently active.
How often the sync fires. ISO 8601 duration. Owned by the sync config on auto_link schedules — patching it there is rejected.
When the schedule was created.
When the schedule was last updated.
The sync config that bounds this schedule. Set on every schedule, hand-authored ones included — it is what permits the action to sync at all. Use source to tell how a schedule came to exist; null here means only that the schedule predates the field.
How the schedule came to exist: auto_link if its sync config fanned it out, manual if it was hand-authored. This is the discriminator between the two, not sync_config_id. It also decides which fields are patchable: an auto_link schedule takes cadence, start_at and full_sync_after from its sync config.
auto_link, manual, unmapped_value, null The point after which an incremental sync falls back to a full sync. ISO 8601 duration; null when unset. Owned by the sync config on auto_link schedules — patching it there is rejected.
When the schedule was first scheduled to fire; null when unset. Owned by the sync config on auto_link schedules — patching it there is rejected.
When the schedule will next fire; null when unset.
When the schedule last ran; null before its first run.
The status of the most recent run; null before its first run.
The error message from the most recent run, if it failed.
Why the schedule is not currently running even though enabled may be true. sync_config_disabled while its sync config is disabled or has been removed, action_disabled while the action is switched off on the connector profile, auto_link_disabled while auto_link is off on a schedule that auto_link created (hand-authored schedules are unaffected by it), or an account-lifecycle reason such as the linked account being disabled. Only the widest cause currently holding the schedule back is reported, so clearing it may reveal another. The schedule keeps its own enabled value throughout. null means nothing is holding it back.