> 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/partially-update-a-rejection-reason.md).

# Partially update a rejection reason

Updates one or more fields of a rejection reason. Send `{"is_active": false}` to retire a reason: it can no longer be cited when rejecting, and past rejections keep pointing at it.

```json
{"openapi":"3.1.0","info":{"title":"Admin API","version":"1.0.0"},"tags":[{"name":"Conversation Rejection Reasons","description":"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.\n\n## Core Capabilities\n\n**1. Reason Listing**\n* Retrieve a paginated list of reasons, ordered by `code`. There are no filters.\n\n**2. Reason Management**\n* Create, update and retire reasons. Retire a reason with `is_active: false` rather than deleting it.\n\n## Reason Fields\n\n| Field | Type | Description |\n|-------|------|-------------|\n| `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. |\n| `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. |\n| `is_active` | boolean, default `true` | Only active reasons can be cited when rejecting. |\n| `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. |\n\n## Retiring a Reason\n\nA 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.\n\nThe 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`."}],"servers":[{"description":"Omnitron Remote Proxy (external access — recommended)","url":"https://{omnitron_url}/api/v1/remote/{channel_id}","variables":{"omnitron_url":{"default":"sandbox.akinon.com","description":"Omnitron server URL (e.g., {omnitron.akinon.com})"},"channel_id":{"default":"1","description":"The channel identifier the remote request is routed through"}}},{"description":"Commerce API Server (internal / direct access only)","url":"https://{commerce_url}/api/v1","variables":{"commerce_url":{"default":"sandbox.akinon.com","description":"Internal commerce server URL, reachable only from within the Omnitron network"}}}],"security":[{"tokenAuth":[]}],"components":{"securitySchemes":{"tokenAuth":{"type":"apiKey","in":"header","name":"Authorization","description":"Token credential sent in the Authorization header, in the form: `Token <your-token>`. Requires a staff (admin) account."}},"schemas":{"ConversationRejectionReasonPatchRequest":{"type":"object","description":"The body of a partial rejection reason update. Every field may be omitted.","properties":{"code":{"type":"string","maxLength":50,"pattern":"^[-a-zA-Z0-9_]+$","description":"Stable, unique identifier — letters, digits, hyphens and underscores."},"text":{"type":"string","maxLength":255,"description":"The rule's wording."},"is_active":{"type":"boolean","description":"Whether the reason can be cited when rejecting."},"translations":{"type":["object","null"],"description":"`text` in other languages, keyed by language code. The rejection e-mail uses the author's language when it is here, and the stored `text` otherwise. Replaced as a whole when sent."}}},"ConversationRejectionReason":{"type":"object","description":"A published rule a moderator can cite when rejecting a review or question.","properties":{"pk":{"type":"integer","readOnly":true,"description":"The unique identifier of the reason — the value sent as `rejection_reason` when rejecting."},"code":{"type":"string","maxLength":50,"pattern":"^[-a-zA-Z0-9_]+$","description":"Stable, unique identifier used in reports. Returned as `rejection_reason` by the event endpoints."},"text":{"type":"string","maxLength":255,"description":"The rule's wording, shown to the author in the rejection e-mail."},"is_active":{"type":"boolean","description":"Whether the reason can be cited when rejecting. Set `false` to retire it."},"translations":{"type":["object","null"],"description":"`text` in other languages, keyed by language code. The rejection e-mail uses the author's language when it is here, and the stored `text` otherwise. Replaced as a whole when sent."}}},"ValidationError":{"type":"object","description":"Returned when the request contains invalid or missing data. Errors are grouped by the field they apply to: each key is the name of a field from the request and its value is a list of one or more messages describing what is wrong with that field. Messages that do not belong to any single field are grouped under `non_field_errors`.","properties":{"non_field_errors":{"type":"array","description":"Error messages that apply to the request as a whole rather than to a specific field.","items":{"type":"string"}}},"additionalProperties":{"type":"array","description":"The list of error messages for the field named by the key.","items":{"type":"string"}}},"Error":{"type":"object","description":"An error response.","properties":{"detail":{"type":"string","description":"A human-readable description of the error."}},"additionalProperties":true}},"responses":{"ValidationError":{"description":"The request contains invalid or missing data.","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ValidationError"}}}},"Unauthorized":{"description":"Authentication credentials were not provided or are invalid.","content":{"application/json":{"schema":{"$ref":"#/components/schemas/Error"}}}},"Forbidden":{"description":"The authenticated user does not have administrator privileges.","content":{"application/json":{"schema":{"$ref":"#/components/schemas/Error"}}}},"ConversationRejectionReasonNotFound":{"description":"No conversation rejection reason exists with the given identifier. Retired reasons (`is_active: false`) are still retrievable, so this answer means the record does not exist at all. An identifier that is not a number is answered with `Not found.` instead.","content":{"application/json":{"schema":{"$ref":"#/components/schemas/Error"}}}}}},"paths":{"/conversation-rejection-reasons/{id}/":{"patch":{"tags":["Conversation Rejection Reasons"],"operationId":"partialUpdateConversationRejectionReason","summary":"Partially update a rejection reason","description":"Updates one or more fields of a rejection reason. Send `{\"is_active\": false}` to retire a reason: it can no longer be cited when rejecting, and past rejections keep pointing at it.","requestBody":{"required":true,"content":{"application/json":{"schema":{"$ref":"#/components/schemas/ConversationRejectionReasonPatchRequest"}}}},"responses":{"200":{"description":"The updated rejection reason.","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ConversationRejectionReason"}}}},"400":{"$ref":"#/components/responses/ValidationError"},"401":{"$ref":"#/components/responses/Unauthorized"},"403":{"$ref":"#/components/responses/Forbidden"},"404":{"$ref":"#/components/responses/ConversationRejectionReasonNotFound"}}}}}}
```


---

# 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/partially-update-a-rejection-reason.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.
