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

# Recart Public API

Learn more about the Recart Public API and its features

### What is the Recart Public API?

* The Recart Public API provides structured and effective communication protocols for web services across e-commerce platforms.
* This API enables automation and enhances user engagement through a suite of tools designed for managing flows, updating carts, processing orders, handling subscriptions, triggering events, and sending messages.

### Key Features

**1. Flow Management:**  Manage marketing and operational flows. Facilitate the listing and retrieval of flow details.

**2. Cart Updates:**  Enable updates to shopping carts with functionality for cart recovery and modifications.

**3. Order Processing:**  Facilitate the creation, updates, and management of orders.

**4. Subscription Services:**  Manage SMS marketing subscriptions with options for both opt-in and opt-out.

**5. Event Handling:**  Post custom events to initiate specific business processes.

**6. Messaging:**  Send SMS/MMS messages to subscribers, supporting both marketing and transactional communications with structured message data.

**7. Webhooks:**  Utilize webhooks to automate responses and integrate seamlessly with external services.

**8. Security and Authentication:**  Secure access to the API is achieved through API key authentication. Each request must include an API key in the header, ensuring all interactions are secure and authenticated.

### **Documentation & Changelog**

For full endpoint details, request and response formats, examples & the changelog — see the [Recart Developers](https://help.recart.com/developers/) section.&#x20;

If you have any questions, do not hesitate to [contact the Recart Support team.](/contact-recart-support.md)  We'd be happy to help!


---

# 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.recart.com/general/recart-public-api.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.
