Bestellungen auflisten
Retrieve orders (purchase and sale) associated with your company, each hydrated with the DDS statements linked to it (ddsReferences). This is the read-back path for an ERP integration: push orders with POST /api/orders, then read them here to collect the TRACES reference and verification number for each order, keyed by your own orderNumber.
All query parameters are optional. A request with none returns every order for your company. Malformed parameter values are rejected with 400 rather than ignored, so a polling integration can never silently receive the full set in place of the subset it asked for.
Autorisierungen
API key generated in Settings > API Keys. Include as Authorization: Bearer <key>.
Abfrageparameter
Restrict to orders that already have a DDS statement linked (true), or to orders that have none yet (false). Note this means a DDS is linked, not that it has been submitted to TRACES — a linked but unsubmitted DDS appears with an empty referenceNumber.
Comma-separated list of order numbers to return, e.g. ORD-1,ORD-2. Maximum 1000 values. Pass the parameter once — repeating the key is rejected rather than silently using only the first value. An empty list is rejected with 400.
Maximum number of results to return. Omit to return all orders — unlike /api/articles, this endpoint applies no default limit.
x >= 1Number of results to skip for pagination. Results are returned in a stable total order, so paging with limit and offset never skips or repeats an order.
x >= 0Antwort
List of orders
purchase = inbound order from a supplier, sale = outbound order to a customer
purchase, sale Sum of all order line quantities
DDS statements linked to this order