Swagger Petstore - OpenAPI 3.0
GET/api/ordering/recurring/{id}/occurrences

One standing order's ledger

A flat ascending window for one standing order — the client splits upcoming from history itself. Defaults to 90 days back through the end of the materialization horizon.

3 parameters
idstringrequired
Standing-order id.
fromstringoptional
Start of an inclusive window, `yyyy-mm-dd`.
tostringoptional
End of an inclusive window, `yyyy-mm-dd`. A range may cover at most 92 days — a wider one is refused, not truncated.

5 status codes
200The occurrences.
idstringoptional
recurringOrderIdstringoptional
recurringOrderNamestringoptional
customerIdstringoptional
customerNamestringoptional
occurrenceDatestringoptional
The DELIVERY day this fire is for — which becomes the generated order's `requestedDeliveryDate`.
statusstringoptional
`scheduled` = due · `generated` = fired · `skipped` = a HUMAN took it out · `cancelled` = the SYSTEM did.
Allowed:scheduledgeneratedskippedcancelled
cancelReasonstringoptional
Why the system cancelled it. Never rendered as a status. `missed` means the day passed with no run — a past day is NEVER generated late.
Allowed:pausedschedule_changedmissed
generatedOrderIdstringoptional
The order this fire produced.
generatedOrderNumberstringoptional
Snapshot taken inside the generating transaction. The history rail labels its jump-to-order button with this.
resolvedAtstringoptional
400Invalid input — the `error` string says what was wrong.
errorstringrequired
401Not authenticated. Sign in first (see the Auth tag).
errorstringrequired
404Not found.
errorstringrequired
500Unexpected server error.
errorstringrequired

Error handling

A 400 is returned: Invalid input — the error string says what was wrong. A 401 is returned: Not authenticated. Sign in first (see the Auth tag). A 404 is returned: Not found. A 500 is returned: Unexpected server error.