> For the complete documentation index, see [llms.txt](https://help.orderdesk.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.orderdesk.com/api-documentation/v2-api-reference/move-orders/move-orders.md).

# Move Orders

Move orders to a new folder. This can target one order or multiple orders.

Please note that either `destination_folder_id` or `destination_folder_name` should be used, but not both. A folder name must match exactly.

The response contains a `results` array with one entry per order, including the folder that each order was moved from.

{% hint style="info" %}
Moving an order triggers any rules assigned to the destination folder and adds an entry to the order's history.
{% endhint %}

```json
{"openapi":"3.0.3","info":{"title":"Order Desk API","version":"2.0"},"tags":[{"name":"Move Orders"}],"servers":[{"url":"https://app.orderdesk.me/api/v2","description":"Production"}],"security":[{"OrderDeskStoreId":[],"OrderDeskApiKey":[]}],"components":{"securitySchemes":{"OrderDeskStoreId":{"type":"apiKey","in":"header","name":"ORDERDESK-STORE-ID","description":"Your store ID, found under Store Settings on the API tab."}},"schemas":{"MoveOrdersRequest":{"type":"object","required":["order_id_list"],"properties":{"order_id_list":{"type":"array","minItems":1,"description":"An array of Order Desk's internal order IDs.","items":{"type":"integer"}},"destination_folder_id":{"type":"integer","description":"The folder ID to which the orders should be moved."},"destination_folder_name":{"type":"string","description":"The name of the folder to which the orders should be moved. It must match exactly.\n"}}},"ResponseEnvelope":{"type":"object","required":["status"],"properties":{"status":{"type":"string","enum":["success","error"],"description":"Either `success` or `error`."},"message":{"type":"string","description":"Describes the result. Always present when an error occurs."},"execution_time":{"type":"string","description":"Time taken to process the request."}}}},"responses":{"BadRequestMoveOrders":{"description":"The move was rejected.","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ResponseEnvelope"}}}},"Unauthorized":{"description":"Authentication failed. See the Authentication guide, and\nnote that an invalid store ID blocks your store rather than simply\nfailing the request.\n","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ResponseEnvelope"}}}},"RateLimited":{"description":"You are sending too fast. Wait `X-Retry-After` seconds. See\nthe Rate Limits guide.\n","headers":{"X-Tokens-Remaining":{"description":"Number of request tokens currently available.","schema":{"type":"integer"}},"X-Retry-After":{"description":"Seconds to wait before requests can resume.","schema":{"type":"integer"}}},"content":{"application/json":{"schema":{"$ref":"#/components/schemas/ResponseEnvelope"}}}},"Error":{"description":"The request could not be completed.","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ResponseEnvelope"}}}}}},"paths":{"/move-orders":{"post":{"tags":["Move Orders"],"summary":"Move Orders","description":"Move orders to a new folder. This can target one order or multiple orders.\n\nPlease note that either `destination_folder_id` or `destination_folder_name`\nshould be used, but not both. A folder name must match exactly.\n\nThe response contains a `results` array with one entry per order, including the\nfolder that each order was moved from.\n\n{% hint style=\"info\" %}\nMoving an order triggers any rules assigned to the destination folder and adds\nan entry to the order's history.\n{% endhint %}\n","operationId":"moveOrders","requestBody":{"required":true,"content":{"application/json":{"schema":{"$ref":"#/components/schemas/MoveOrdersRequest"}}}},"responses":{"200":{"description":"The orders were moved.","content":{"application/json":{"schema":{"allOf":[{"$ref":"#/components/schemas/ResponseEnvelope"},{"type":"object","properties":{"results":{"type":"array","items":{"type":"object","properties":{"order_id":{"type":"integer"},"message":{"type":"string"},"original_folder_id":{"type":"integer","description":"The folder the order was moved from."}}}}}}]}}}},"400":{"$ref":"#/components/responses/BadRequestMoveOrders"},"401":{"$ref":"#/components/responses/Unauthorized"},"429":{"$ref":"#/components/responses/RateLimited"},"default":{"$ref":"#/components/responses/Error"}}}}}}
```


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://help.orderdesk.com/api-documentation/v2-api-reference/move-orders/move-orders.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.