> This page is for API Reference.

> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://fiftytwo-demo.ferndocs.com/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://fiftytwo-demo.ferndocs.com/_mcp/server.

# About the Order API

The Order API exposes endpoints for order requests: the orders a customer places
in one channel and fulfils through a store.

## Endpoints

| Method  | Path                                                                             | Purpose                         |
| ------- | -------------------------------------------------------------------------------- | ------------------------------- |
| `POST`  | `/orders/v1`                                                                     | Save an order to the database   |
| `GET`   | `/orders/v1`                                                                     | Retrieve all unprocessed orders |
| `GET`   | `/orders/v1/orderid/{orderId}`                                                   | Retrieve one order request      |
| `GET`   | `/orders/v1/collectchainnum/{collectchainnum}`                                   | Unprocessed orders for a chain  |
| `GET`   | `/orders/v1/collectchainnum/{collectchainnum}/collectstorenum/{collectstorenum}` | Unprocessed orders for a store  |
| `PATCH` | `/orders/v1/orderid/{orderId}/status/{newStatus}`                                | Update an order's status        |
| `POST`  | `/ordermanagement/v1`                                                            | Order management submission     |

## The collect-side model

The parameters are named `collectchainnum` and `collectstorenum` rather than
`chain` and `store`, and that naming is the point: an order is queried by **where
it will be collected**, not where it was placed.

That is what makes the store-scoped `GET` the natural poll for a store's own
fulfilment queue. A store asks "what do I need to pick today?" and gets exactly
its own unprocessed orders.

> **Note**
>
> Retrieval endpoints return **unprocessed** orders. Advancing an order's status
> with `PATCH` is what removes it from that queue, so status updates are part of
> the contract rather than bookkeeping.

## Related

#### [Order management](/help/concepts/order-mgt)

How 52ViKING models order management.

#### [Unified commerce](/help/unified-commerce/mp)

Where click & collect fits in the wider platform.