Scheduling
Scheduling is how a change happens later. A price rise on 1 January, a plan version going live at midnight, a cancellation at period end: all of them are recorded now and applied then.
Kontier holds these as scheduled changes, in one list, so "what is about to happen to this customer" is a question with an answer.
Why not just edit it later
Because somebody has to remember, and because the change must be visible before it happens.
A scheduled change is auditable in advance: the customer's next bill can be explained before it is issued, support can see what is queued, and a mistake can be cancelled rather than reversed after the fact.
What you can do to one
| Action | Endpoint |
|---|---|
| Inspect what will change | GET /scheduled-changes/{id}/diff |
| Apply it now, early | POST /scheduled-changes/{id}/release |
| Move it to a different date | PUT /scheduled-changes/{id}/reschedule |
| Undo one already applied | POST /scheduled-changes/{id}/rollback |
| Cancel many at once | POST /scheduled-changes/bulk-cancel |
diff is the one to reach for first. It answers "what exactly will this do"
without applying anything, which is the question you actually have.
Rollback is not the same as cancel
Cancel stops something that has not happened. Rollback undoes something that
already has, which may mean an invoice has been issued under the new terms.
Check diff and the effective date before choosing.
Flow templates
A schedule flow template is a reusable sequence: a set of changes that always happen together, in order.
GET /v1/schedule-flow-templates/starters lists ready-made ones, and
POST .../starters/{key}/adopt copies a starter into your organisation so you
can edit it. POST /schedule-flow-templates/{id}/instantiate runs a template
against a target.
Use them for anything you do repeatedly, such as a standard onboarding ramp or a renewal sequence.
Where scheduling goes next
- Plan versions publish through it. That is why publishing is a scheduled release rather than an immediate write.
- Subscription changes land here when they carry an
effective_atin the future. - Tax rules are versioned and dated for the same reason.
Reference
| Topic | When you need it |
|---|---|
| Plans | Publishing a version, and moving subscribers |
| Subscriptions | Plan moves and quantity changes with a later date |
| Scheduled changes API | Diff, release, reschedule, rollback |