Actions28
- Inbound Order Actions
- Order Actions
- Order Return Actions
- Product Actions
- Shipment Actions
- Stock Actions
Inbound Order → Confirm
AI-generatedSummary
Create an inbound confirmation document in Linker Cloud by sending the supplier, dates, totals, items, and optional confirmation details to the supplier orders confirms endpoint.
Inputs
- Order Date (required) — Confirmation document date in YYYY-MM-DD HH:mm:ss format.
- Execution Date (required) — Execution date in YYYY-MM-DD HH:mm:ss format.
- Price Gross (required) — Total gross price.
- Price Net (required) — Total net price.
- Supplier (required) — Supplier name.
- Supplier Object (required) — Supplier details as a JSON object; the value must be valid JSON.
- Items Input Mode — Choose manual UI entry or JSON. UI items accept EAN, name, unit price, quantity, and SKU; quantity and SKU are marked required. JSON mode expects a valid JSON array of items, with SKU, quantity, and price described as the item fields.
- Additional Fields — Optional confirmation details: assigned fulfillment site, auto number, client order number, comments, currency symbol (defaults to PLN), custom properties (JSON array), depot ID, installment, return flag, container/pallet/parcel counts, priority, and supplier ID.
Output shape
A single item containing the API response as JSON.
The operation sends a POST request to /public-api/v1/supplierorders/confirms. Custom Properties is parsed from JSON and defaults to an empty array; Supplier Object and JSON-mode Items must also contain valid JSON. With Continue On Fail enabled, an item with an error field is returned for a failed input.