> 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-rejection-reasons.md).

# Conversation Rejection Reasons

Administrative endpoints for **conversation rejection reasons** — the published rules a moderator cites when rejecting a review or question (for example profanity, personal data, or content unrelated to the product). Every rejection must cite one active reason, so at least one must exist before anything can be rejected.

### Core Capabilities

**1. Reason Listing**

* Retrieve a paginated list of reasons, ordered by `code`. There are no filters.

**2. Reason Management**

* Create, update and retire reasons. Retire a reason with `is_active: false` rather than deleting it.

### Reason Fields

| Field          | Type                              | Description                                                                                                                                                                                                                                                    |
| -------------- | --------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `code`         | slug, unique, up to 50 characters | Stable identifier. Reports and the **Conversation Events** feed return it as `rejection_reason`, so keep it unchanged once used.                                                                                                                               |
| `text`         | string, up to 255 characters      | The rule's wording. Shown to the author in the rejection e-mail and returned as `rejection_reason_text`. Events refer to the reason rather than copying it, so an edit changes the wording shown for past rejections too; e-mails already sent are unaffected. |
| `is_active`    | boolean, default `true`           | Only active reasons can be cited when rejecting.                                                                                                                                                                                                               |
| `translations` | object or `null`                  | `text` in other languages, keyed by language code — for example `{"en-us": {"text": "Posts must not contain profanity."}}`. Replaced as a whole when sent.                                                                                                     |

### Retiring a Reason

A reason that a rejection has already cited cannot be deleted: the request is refused with `406` and nothing is removed. Set `is_active` to `false` instead — the reason can no longer be cited, and past rejections keep pointing at it. A reason that was never cited can be deleted.

The rejection e-mail cites the reason in the author's language: its translation when `translations` has one for that language, the stored `text` otherwise. These endpoints return the stored `text` alongside `translations`, and `rejection_reason_text` on events is always the stored `text`.


---

# 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-rejection-reasons.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.
