> For the complete documentation index, see [llms.txt](https://developers.alephee.com/v2/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developers.alephee.com/v2/orders/get-methods/get-orders-list-from-a-shopping-cart/response.md). # Type specifications ## OrdersPack | Property | Type | Description | | ---------------- | ---------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Id | integer |

Shopping cart number associated with the order. Only if the order is part of a shopping cart purchase.

Please refer to the above notes.

| | ~~SourcePackId~~ | ~~string~~ | The original shopping cart number associated with the order. | | IsComplete | bool |

When TRUE, the order is a shopping cart purchase and all items in the cart are present and available for download.

When FALSE, the order is a shopping cart purchase and NOT all items in the cart are present and available for download. You need to wait a while for all the items in the cart to arrive from the marketplace of origin and try to download the order again.

Please refer to the above notes.

| | Marketplace |

{

Key (integer),

Value (string),

Channel (string)

}

|

ID of the marketplace in which the order originated.


See marketplaces ID section and the GET marketplaces endpoint for the coding reference.

Channel property is available on the following scenarios:

· Mercado Libre: When the sale came from a “Mercado Shops” sale the string contains this name.

All individual orders in the same shopping cart share the same marketplace information. This ORDERS PACK displays that information once and is not repeated for each individual order.

| | SellerAccount | [Type specifications](/v2/orders/get-methods/get-orders/response.md#seller) |

The seller to whom the orders belong to.

All individual orders in the same shopping cart share the same seller information. This ORDERS PACK displays that information once and is not repeated for each individual order.

| | Buyer | [Type specifications](/v2/orders/get-methods/get-orders/response.md#buyer) |

Buyer details.

All individual orders in the same shopping cart share the same buyer information. This ORDERS PACK displays that information once and is not repeated for each individual order.

| | Payments | [Type specifications](/v2/orders/get-methods/get-orders/response.md#payment) |

List of payments.

All individual orders in the same shopping cart share the same payments information. This ORDERS PACK displays that information once and is not repeated for each individual order.

| | Shipping | [Type specifications](/v2/orders/get-methods/get-orders/response.md#shipping) |

Shipping details.

All individual orders in the same shopping cart share the same shipping information. This ORDERS PACK displays that information once and is not repeated for each individual order.

| | Total | integer | The quantity of individual orders belonging to the shopping cart. | | Orders | [Type specifications](/v2/orders/get-methods/get-orders/response.md#order) |

The collection of individual orders belonging to the shopping cart.

Please note that the following properties from OrderType object are not visible:

· Marketplace

· SellerAccount

· Buyer

· Payments

· Shipping

That happens because those properties are already present in this JSON, and it doesn't make sense to repeat them in each individual order.

| --- # 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://developers.alephee.com/v2/orders/get-methods/get-orders-list-from-a-shopping-cart/response.md?ask=&goal= ``` `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.