/api/ordering/recurring/{id}Update a standing order
Updates a standing order by replacing its full schedule and line set. Supply the complete template on each request, including customerId, name, daysOfWeek, and lines; the ledger is reconciled in the same transaction. Past occurrences and generated or skipped rows remain unchanged, while future scheduled occurrences are reconciled to the updated schedule.
- IdempotentThe SDK sends
Idempotency-Key, so a retried request is only applied once.
The complete standing-order template. customerId, name, daysOfWeek, and lines are required; server-derived fields and line id values are rejected.
A 400 is returned for invalid input, including omitted required fields, server-derived fields in the request, or values that fail validation; a 401 is returned when the authenticated user is not signed in. A 403 is returned when the authenticated user lacks the required department membership or role, a 404 is returned when the standing order is not found, and a 500 is returned for an unexpected server error. The id path parameter must identify an existing standing order. customerId, name, daysOfWeek, and lines are required; daysOfWeek must contain at least one integer from 0 to 6, each line must include itemId, qty, rawBaked, loosePacked, and sliced, and qty must be greater than 0. pausedUntil, when supplied, must be a date strictly after today; do not send server-derived fields or line id values.