Skip to main content

Create SKU Orders from Amazon Orders

POST 
/api/amazon/:integrationInstance/orders/create-sku-orders

Create SKU.io sales orders from this instance's Amazon orders. Runs synchronously.

Authorization

Any valid API token can call this endpoint — no specific scope required. Manage tokens.

Body fields:

  • ids (array of integers, optional) — internal Amazon order record IDs (the SKU.io row ids, not Amazon marketplace order numbers) to convert. When specific ids are given, the configured order start-date restriction is bypassed and the response includes the created sales orders.
  • create_all_orders (boolean, default false) — set true to convert all pending orders regardless of the integration's configured order start date (the "Create All" behaviour).
  • filters (string, optional) — JSON string in the same flat-filter format as the orders list ({"conjunction","filterSet":[...]}). When present, ids is overwritten server-side with the order ids matching the filter set for this instance.

When neither ids nor create_all_orders is provided, all pending orders dated after the integration's configured order start date are converted. For each created sales order, automated fulfillment rules are evaluated by a background job. When specific ids all fail to convert, a 422 is returned with the first failure reason (for example an unmapped product, or an order currency that does not exist in Settings > Currencies).

Bulk selection contract:

  • {"ids": [1, 2]} — create for the given channel order IDs
  • {"create_all_orders": true} — create for all eligible orders on the integration instance
  • {"create_all_orders": true, "filters": {...}} — create only for orders matching the filters. The filters object accepts the same filter keys as the corresponding orders list endpoint (bare column keys, e.g. {"order_status": "pending"}) and/or a "filter_groups" tree (base64-encoded JSON, same format as the list endpoint). When filters match no orders, nothing is created and the response message is "No orders to create".
  • Legacy {"conjunction", "filterSet"} filter payloads are rejected with 422.

Request​

Responses​

OK

Response Headers
    Content-Type