Recurring Schedules
Not available through the public API
This page describes a planned capability. It has no endpoints in the public API
today, and nothing on this page can be called. To schedule a one-off future action today, such as publishing a catalog version or changing a subscription at a date, use POST /v1/changes; see Scheduling.
A recurring schedule would be a cron-style trigger that fires a chosen action on a repeating cadence, such as a monthly partner settlement run, a weekly usage summary email or a periodic reconciliation export, and keeps firing until you pause or delete it.
Planned model
The shape below is planned and may change before release. None of it is part of any API today.
| Field | Description |
|---|---|
name | Human-readable label |
cron | Standard 5-field cron expression |
timezone | IANA timezone the cron is interpreted in |
action_type | The action to fire, for example a settlement run or a report email |
action_config | Per-action payload |
status | active, paused |
next_run_at | When the schedule would fire next |
A schedule could be paused and resumed, a failed run would be recorded in the schedule's run history without delaying the next one, and the action itself would own any retry logic.
Next steps
- Scheduling - one-off future changes, available today
- Settlements - a planned action target