---
title: "Order Confirm"
method: PUT
path: "/v1/seller/order/accept"
tags: ["Order"]
---

# Order Confirm

`PUT /v1/seller/order/accept`

Accept Order with Stauts `UNACKED`.

## Request body

- OrderAccept — Batch of seller order confirmations — acknowledges that the listed orders will be fulfilled.
  - `orderList` object[]
    - `channel` string, required — This is the unique Channel name.
    - `sellerId` string, required — A unique Id identify a Seller on a specific SalesChannel. The SellerId is generated from the Channel itself during the Seller SignUp Process.
    - `orderId` string, required
    - `orderAccepted` boolean
    - `reason` 'BUYER_CANCELLED' | 'UNDELIVERABLE_TO_SHIPPING_ADDRESS' | 'UNDELIVERABLE_BY_CARRIER' | 'OUT_OF_STOCK' | 'DELAYED_INVENTORY' | 'PRICING_ERROR' | 'OTHER' — * BUYER_CANCELLED: the buyer cancelled the order. * UNDELIVERABLE_TO_SHIPPING_ADDRESS: Could not deliver to the address given by the buyer. * UNDELIVERABLE_BY_CARRIER: Carrier do not ship to the buyerss location. * OUT_OF_STOCK: The item is out of stock, for example because you are temporarily or permenantly sold out. * DELAYED_INVENTORY: The item is not in your inventory and there is a delay in delivery by the supplier. * PRICING_ERROR: The price on the connected marketplace was incorrect. * OTHER: Well, objvoiusly there is some reason missing in this list.

## Response `201`

Created

## Other responses

- `400` — Bad Request
- `401` — Access forbidden, invalid or unknown Token was used.
- `429` — User has send to many requests
- `500` — Unexpected Server Error

---

[API](https://skmtc.net/jtl-software/apis/scx-authentication-api.md) · [All operations](https://skmtc.net/jtl-software/apis/scx-authentication-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/jtl-software/scx-authentication-api/revisions/f979b1ea6951/schema)