Item Feed (Picked-Nilpicked-Unpicked) Notification Webhook

This webhook request notifies recipients that the shopper or picker could/could not pick the customer-ordered item in the store/location.
It notifies recipients that the shopper or picker removed the customer-ordered item from the picked items already gathered for the order.

Use of this webhook requires the integrator to provide an endpoint. Webhook events are published to client-provided endpoints.

Body Params

Request for item feed

string
required

Specifies the type of event.

Example

ORDER_ITEM_FEED

string
required

Specifies the event name.

Example

ORDER_ITEM_PICK

ORDER_ITEM_UNPICK

ORDER_ITEM_NILPICK

string
required

Specifies an identifier for the event.

Example

6f570da6-ead5-3aea-8bff-9c4c8ae59920

cafa7f3a-e75a-3c2d-8da5-e54871ec5c9d

a6ae8b9b-c9a7-3a6a-9655-dc91384ab5c7

date-time
required

Specifies the date-timestamp of generated time event, in ISO 8601 format.

Example

2022-05-16T04:20:09.944Z

string
required

Specifies the Store Assist fulfillment order number.

Example

135246

int64
required

Specifies the pick walk identifier generated by the picking system.

Example

463073

463081

0

string
required

Specifies the type of the pick walk, to include INITIAL, NORMAL, EXCEPTION, and EXPRESS.

Example

INITIAL

NORMAL

EXCEPTION

EXPRESS

string
required

Specifies an identifier for the customer order.

A single customer order can have multiple items, and those items can be available in different stores. As such, tenants can break a single customer order (CO) identifier into multiple purchase order (PO) numbers that reflect the different stores and order types.

Example

MAK4231

881627941728831

string
required

Specifies a valid store or location number.

Example

2771

1107

2770

items
array of objects
required
items*
Headers
string
required

Specifies the external identifier of the client store.

Example

9221

Response
200

ORDER_ITEM_FEED webhook sent successfully

Language
Response
Click Try It! to start a request and see the response here!