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

# Carts

Read shopping carts and their configured product selections. A cart can be open or submitted; its submission details become available after it is submitted.

Use carts to retrieve a submitted enquiry or order input for another system, including contact information, selected configurations, quantities and prices. A cart is distinct from a quotation and does not by itself confirm a completed sale.

### What you can do

| Task                 | Reference                                                         |
| -------------------- | ----------------------------------------------------------------- |
| Find available carts | [List Carts](https://help.mimeeq.com/developers/carts/list-carts) |
| Read one cart        | [Get Cart](https://help.mimeeq.com/developers/carts/get-cart)     |

### Before you start

Your API key needs `carts:read` to read these resources.

### Important behaviour

These endpoints are read-only. List Carts requires at least one filter: status, `companyId` or `contactId`. Company and contact filters cannot be combined. Use Get Cart for the full line items, price modifiers and submission data; submission-specific values are null while the cart is open.


---

# 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://help.mimeeq.com/api/carts.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.