The single-call way for integrators to create an order: send your shop `orderid`, the shipping address and one or more lines with a `sku` and print-file URLs. The order is created as a **PENDING draft** — nothing is charged until it is submitted (send `"submit": true`, call **Submit order**, use **Create order + submit**, or submit in the portal). **Two flows, chosen by `createProducts`.** • **Default (`createProducts` omitted or false).** Each line is matched to a catalog product for that `sku` (found or created) and the order is created in the same request. The response is `data = { products, order, submit? }` — read the order from `data.order`. With `"submit": true` the wallet is charged **in the same request** and `data.submit` is `{ orderId, status: "PAID" }`. Sending the same `orderid` again returns the existing order (HTTP 200) instead of a duplicate — safe to retry. • **`createProducts: true`.** A new catalog product is created for every line and the print files are downloaded in the background. The response comes back in about a second with the order itself in `data` plus `assets: "PROCESSING"`; follow it with **Print-file status** until `READY` or `FAILED`. Here a repeated `orderid` is refused with HTTP 409 (code 2003) whatever the state of the earlier order. Needed for per-line `printingMethod`, `sellingPrice`, `largeFormatAreas`, `hasSpecialPrintArea` and neck labels. **Freeing an orderid.** Orders cannot be cancelled through the API. To reuse an `orderid`, delete the draft with **Delete draft order** while it is still PENDING; after payment, open a settlement request instead. **Printing method.** Some product types can only be produced once a printing method (for example DTG, DTF or inkjet) is set. The method is normally resolved from the `sku` (see `defaultPrintingMethod` / `printingMethodRequired` in **List SKU reference**). If the API answers `This provider requires a decoration method (e.g. DTG, DTF). Please select a printing method for the product.`, send the request again with `"createProducts": true` and add `printingMethod` to that line, e.g. `"printingMethod": "Inkjet printing"`. The failed request created no order, so you can retry with the same `orderid`. Common printing-method errors: • `products[N].printingMethod requires "createProducts": true …` → add `"createProducts": true` at the top level of the body. • `products[N]: printing_method "…" was not found … — options: …` → send one of the listed options. • `Invalid JSON body` → check value types: `createProducts` and `submit` must be JSON booleans and `quantity` a JSON number. **Per line** (see the `products` parameter): `sku` and `designUrlsByArea` are required; `blueprintId` (only to tell apart a `sku` that matches several catalog rows), `productId` and `providerBlueprintId` are optional and ignored when `createProducts` is true. Order-list previews go in `mockupFrontUrl` / `mockupBackUrl` / `mockupNeckInnerUrl`. Legacy V1 aliases (`firstname`, `zipcode`, `methodship`, `areafront`, …) are still accepted. The order is tagged with the calling API key (`apiKeyId`, `apiKeyName`). A team member limited to API-key orders cannot create orders (code 1003). See Guides → Access & permissions and Guides → Orders & fulfillment.