> For the complete documentation index, see [llms.txt](https://docs.hotwax.co/documents/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hotwax.co/documents/integrate-with-hotwax/hotwax-commerce-api-and-data-feeds/fulfillment/create-picklist.md).

# Create Picklist

Learn how to create picklists for order item pickups efficiently within the 'Brokering WIP' documentation.

Creates a picklist of the order items to be picked up. To create a picklist, you will need to call the /createPicklist endpoint with the POST method.

## Request

### Endpoint

`https://<host>/api/createPicklist`

Example: <https://demo-oms.hotwax.io/api/createPicklist>

### Header

#### Body

```
facilityId: WH
facilityId_o_0: WH
shipmentMethodTypeId_o_0: STANDARD
itemStatusId_o_0: PICKITEM_PENDING
shipGroupSeqId_o_0: 00002
orderId_o_0: 10175
orderItemSeqId_o_0: 00101
productId_o_0: 10002
quantity_o_0: 1
inventoryItemId_o_0: 10120
picked_o_0: 1
_rowSubmit_o_0: Y
pickerIds: 10000
```

Note: Pass the data in form format.

| Parameter                  | Description                        | Required (Y/N) |
| -------------------------- | ---------------------------------- | -------------- |
| `facilityId`               | The ID of the facility             |                |
| `facilityId_o_0`           | The ID of the picklist bin         |                |
| `shipmentMethodTypeId_o_0` | The ID of the shipment method type |                |
| `itemStatusId_o_0`         | The ID of the item status          |                |
| `shipGroupSeqId_o_0`       | The ID of the ship group sequence  |                |
| `orderId_o_0`              | The ID of the order                |                |
| `orderItemSeqId_o_0`       | The ID of the order item sequence  |                |
| `productId_o_0`            | The ID of the product              |                |
| `quantity_o_0`             | The quantity of the items          |                |
| `inventoryItemId_o_0`      | The ID of the inventory item       |                |
| `picked_o_0`               | The number of items to be picked   |                |
| `_rowSubmit_o_0`           |                                    |                |
| `pickerIds`                | The ID of the picker               |                |

## Response

### Header

#### Body

```
{
    "quantity_o_0": "1",
    "orderItemSeqId_o_0": "00101",
    "picklistId_o_0": "10112",
    "facilityId_o_0": "WH",
    "shipGroupSeqId_o_0": "00002",
    "orderId_o_0": "10175",
    "picklistBinId_o_0": "10122",
    "facilityId": "WH",
    "pickerIds": "10000",
    "picked_o_0": "1",
    "shipmentMethodTypeId_o_0": "STANDARD",
    "inventoryItemId_o_0": "10120",
    "itemStatusId_o_0": "PICKITEM_PENDING",
    "picklistId": "10112",
    "picklistBinId": "10122",
    "_rowSubmit_o_0": "Y",
    "productId_o_0": "10002"
}

```

| Parameter           | Description                |
| ------------------- | -------------------------- |
| `picklistId_o_0`    | The ID of the picklist     |
| `picklistBinId_o_0` | The ID of the picklist bin |
| `itemStatusId_o_0`  | The ID of the item status  |
| `picklistId`        | The ID of the picklist     |
| `picklistBinId`     | The ID of the picklist bin |
| `productId_o_0`     | The ID of the product      |


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.hotwax.co/documents/integrate-with-hotwax/hotwax-commerce-api-and-data-feeds/fulfillment/create-picklist.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.