/api/ordering/recurringCreate a standing order
Creates a standing order template and materializes its occurrence horizon in the same transaction. Supply customerId, name, daysOfWeek, and lines; line quantities and preparation options define the template. The response may include a non-blocking warning about an overlapping weekday order or a generation run that has already passed.
- 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, and a 500 is returned for an unexpected server error. customerId, name, daysOfWeek, and lines are required; daysOfWeek must contain at least one integer from 0 to 6, and each line must include itemId, qty, rawBaked, loosePacked, and sliced. qty must be greater than 0, the preparation fields must use their documented enum values, and pausedUntil, when supplied, must be a date strictly after today; do not send server-derived fields or line id values.