> For the complete documentation index, see [llms.txt](https://apidocs.akinon.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://apidocs.akinon.com/commerce-openapis/admin/conversations/conversation-messages.md).

# Conversation Messages

A single endpoint for **appending a message** to an existing conversation — a seller's answer to a question, or either side's next message in a private conversation. To open a new conversation, use `POST /conversations/`.

Unlike the rest of this section, it is not limited to staff. The customer who owns a conversation may call it signed in as themselves, but only in their own name. Staff write as the conversation's seller, or in a customer's name.

### What Each Kind Accepts

| Kind       | Seller message (`content_type: datasource`)                    | Customer message (`content_type: user`)                      |
| ---------- | -------------------------------------------------------------- | ------------------------------------------------------------ |
| `review`   | Refused — a review cannot be replied to (`conversation_100_9`) | Refused — a review is written once (`conversation_100_10`)   |
| `question` | Accepted — the seller's answer                                 | Refused — a question is written once (`conversation_100_10`) |
| `message`  | Accepted                                                       | Accepted                                                     |

Refusals are answered with `406`; see **Errors** under **Conversations**.

### Effects

* **Seller message** — sets `is_answered` to `true` (recording `marked_answered` if it was `false`), records a `replied` event, e-mails the customer with the Conversation Replied template and emits the `conversation_replied` webhook. A seller reply is not moderated: a reply to an approved question appears on the storefront straight away, and a reply to a pending question appears as soon as the question is approved.
* **Customer message** — sets `is_answered` back to `false`, recording `marked_unanswered` if it was `true`.

### Dynamic Settings & Environment Variables

| Key                   | Type                                                 | Default                                    | Effect                                                                                                                                                                                                                                                                                                                                                                                               |
| --------------------- | ---------------------------------------------------- | ------------------------------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `THROTTLING_SETTINGS` | object — scope → `{"count": N, "duration": seconds}` | `send-message`: 10 requests per 60 seconds | The `send-message` scope limits how often each caller — counted per user, or per client IP when unauthenticated — may post a message. The count is shared with the storefront's `/users/conversations/` endpoint, where listing and reading conversations count too. Requests over the limit are answered with `429`, except the first one from a client not yet flagged, which is let through once. |

`DISABLED_EMAIL_TEMPLATES` and `EMAIL_BCC_AND_CC` apply to the reply e-mail as described under **Conversations**.


---

# 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://apidocs.akinon.com/commerce-openapis/admin/conversations/conversation-messages.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.
