try out ↗

← API Index


/api/client/neworder8

Create a new order for a delivery date. If the shop allows only one order per delivery (setup allowmultiorders off, the default) and the customer already has an open order on that date and tour, the request is treated as a change of that order: the posted cart becomes its content and its id is returned, no second order is created (locked -> the one order of that date is in processing). Clients should normally send changeorder for a date that already has an order (see ShopDate.orderId)

Parameters

Name Description Type
ddate_iso delivery date: yyyy-MM-dd, or an ISO 8601 timestamp (2026-10-13T22:00:00.000Z as sent by the JS client, or 2026-10-14T00:00:00+02:00); a timestamp is resolved to its day in the shop's time zone string
tour tour id int
opos order positions as HTTP POST list parameter, one occurance for every order position. Each contain -pipe-delimited- the following values: iid (item id), amount (in units), unit (text form), unitid (negative, if its an alternative unit), aboid (reference if it comes form an abo), isPre (1 if it was already in the order before this modification),note (arbitrary customer note), extref ( a reference to an external info about that position, e.g. a recipe) string
order order data as HTTP POST list parameter string
shot internal: indicates single-shot order mode string
no_clear with this being true, the session (date, cart) does not get cleared (server side cart use case or simple shop boolean
used_paycode payment code the customer indicated for this order (must be one of the customer's allowed paycodes) int
ragb if 1, the customer accepts the terms and conditions (AGB) again with this order and the acceptance date is stored. Send it when UserInfo.needs_tc is 1, i.e. the shop changed its terms (public config key agbChangeDate, hint text agbChangeHint) after the customer's last acceptance. There is no per-order re-approval; the order is stored either way, the client has to insist on the checkbox int
cartnote an optional note (max 255 chars) related to this order string
oo-rf optionally define the response-format for this call. One of: compact (default) | compacts | full | fulls | json | md | html | js | openapi | yaml String
oo-auth optionally force the API to check against the role (instead of silently not returning data). For guests or public access, the default is -1. 0 (regular customer) and above define the role for which the current session is expected to be authorized. int

Error Responses

HTTP Status Error Code Description
409 not_stored General error storing order
409 no_date No delivery date
404 empty No items in order
409 too_late Order stop has passed
409 locked Order is locked
409 protected_items Order contains protected items
409 below_mbw Order is below minimum order value
409 exceeded Order limit exceeded
409 no_change No changes detected
409 duplicate Duplicate order detected
409 insufficient_sales_items Insufficient sales items
409 retry Temporary conflict, retry
403 not_auth User is not authenticated
403 security_error Security violation

Response Types

Type Version Description
ChangeOrderResult 1 Optional Result of a order mutation action (order submission, cancellation, etc.)
ShopDate 8 A delivery date with order, tour, shipping, and address information
Pause 1 A delivery pause period
Subscription 4 A standing subscription (item or assortment box)
Favourite 1 A shelf favourite (bookmarked item or menu level)
AuxDate 1 An auxiliary calendar event or notice
DeselectedItem 1 An item preferably excluded from a customer's assortment
DeselectedGroup 1 A category preferably excluded from a customer's assortment

OpenAPI

See neworder8.yaml

Referenced in skills