> 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/contact-us-subjects/partially-update-a-contact-us-subject.md).

# Partially update a contact us subject

Updates only the fields sent. Outside the default language, `text` is written only as the translation for the request language (see **Translations** and `IGNORE_ACCEPT_LANGUAGE_HEADER` in the section description).

```json
{"openapi":"3.1.0","info":{"title":"Admin API","version":"1.0.0"},"tags":[{"name":"Contact Us Subjects","description":"Administrative endpoints for **contact us subjects** — the subjects a shopper chooses from on the storefront contact form. Each subject decides whether the form must reference an order and which addresses the submitted message is e-mailed to.\n\nThe storefront reads the same records through its own contact form endpoints; these endpoints are for managing them.\n\n## Core Capabilities\n\n**1. Listing**\n* Retrieve a paginated list of subjects. Order the results with the `sort` parameter.\n\n**2. Subject Management**\n* Create a subject, retrieve a single subject, fully (`PUT`) or partially (`PATCH`) update it, and delete it.\n\n## Contact Us Subject Fields\n\n| Field | Type | Description |\n|-------|------|-------------|\n| `pk` | integer | The unique identifier of the subject. Read-only. |\n| `text` | string (max 60) | The subject label shown on the contact form. Translatable (see **Translations**). Required on create and full update; may not be blank. |\n| `is_order_needed` | boolean | Whether the storefront contact form requires an order to be selected for this subject. Required on create; optional on update. |\n| `recipients` | array of e-mail strings, or `null` | The addresses messages sent with this subject are e-mailed to. Each item must be a valid e-mail address of at most 254 characters. The list may be `null` but **not empty** — `[]` is rejected with `400` and `{\"recipients\": [\"...\"]}`. An invalid address is reported under its zero-based index, e.g. `{\"recipients\": {\"0\": [\"Enter a valid email address.\"]}}`. When `null`, the storefront falls back to `CONTACT_US_EMAIL_TO` (see **Dynamic Settings & Environment Variables**). |\n\n## Translations\n\n`text` is translatable. It is written to, and read from, the language selected for the request:\n\n* In the default language (`LANGUAGE_CODE`) the value is stored on the subject itself.\n* **Create** in any other configured language stores `text` both on the subject itself and as the translation for that language.\n* **Update** in any other configured language stores `text` only as the translation for that language; the default-language value is left unchanged.\n* List and retrieve return the translation for the request language, falling back to the default-language value when no translation exists.\n\n`is_order_needed` and `recipients` are shared by all languages. Ordering by `text` always uses the default-language value. Whether the `Accept-Language` header can select the request language is controlled by `IGNORE_ACCEPT_LANGUAGE_HEADER`.\n\n## Form-Encoded Requests\n\nThe write operations also accept `multipart/form-data` and `application/x-www-form-urlencoded` bodies. In a form-encoded create or full update (`PUT`), a missing `is_order_needed` is read as `false` instead of being left out. Send it explicitly, or use JSON.\n\n## Filtering & Ordering\n\nNo filters are available; unknown query parameters are ignored. Use the `sort` parameter to order the results by `pk`, `text`, `is_order_needed` or `recipients` (for example `sort=-pk`); prefix a field with a hyphen for descending order. Other field names are ignored. Without `sort`, results are ordered by `pk`.\n\n## Deleting a Contact Us Subject\n\n`DELETE` is a **hard delete**. The subject is removed immediately and is no longer offered on the storefront contact form.\n\n## Dynamic Settings & Environment Variables\n\n**Dynamic settings** (`dj_dynamic_settings`):\n\n| Key | Type | Default | Effect |\n|-----|------|---------|--------|\n| `IGNORE_ACCEPT_LANGUAGE_HEADER` | boolean | `true` (falls back to the same-named Django setting) | Whether the `Accept-Language` header is discarded before the request is processed. While it is `true`, the header is honored only when the request also carries an `X-Omnitron-Session` header; otherwise the default language is used. Affects **every** operation: the selected language decides which translation of `text` is written by create and update requests and returned by every response (see **Translations**). |\n| `IGNORE_DELETED_ITEMS_SIGNAL` | array of strings | `[\"django_audit_events.AuditEvent\", \"django_audit_events.ArchivedAuditEvent\", \"sessions.Session\", \"datawarehouse.DeletedItem\"]` (falls back to the same-named Django setting) | The model labels excluded from delete tracking. Affects **delete**: unless `users.ContactUsSubject` is added to this list, deleting a subject also records a deleted-item entry for the data-warehouse export. The API response is identical either way. |\n| `CONTACT_US_EMAIL_TO` | object mapping an operation name, or `defaults`, to an e-mail address or a list of addresses | `{\"defaults\": [\"contactus@akinon.com\"]}` (falls back to the `CONTACT_US_EMAIL_TO` env var / Django setting) | The addresses storefront contact form messages are sent to when the chosen subject has no `recipients`. It does not change the requests or responses of these endpoints. |\n\n**Environment variables / Django settings:**\n\n| Setting | Default | Effect |\n|---------|---------|--------|\n| `LANGUAGE_CODE` | `tr-tr` | The default language. `text` written in this language is stored on the subject itself. |\n| `LANGUAGES` | `tr-tr` only | The languages the site supports. A language that is not listed here cannot be selected for a request, so translations for it cannot be written or read. |"}],"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":{"ContactUsSubjectPatchRequest":{"type":"object","description":"Fields of a contact us subject that can be written. In a partial update every field is optional.","properties":{"text":{"type":"string","minLength":1,"maxLength":60,"description":"The subject label, written in the request language (see **Translations** in the section description)."},"is_order_needed":{"type":"boolean","description":"Whether the storefront contact form requires an order to be selected for this subject."},"recipients":{"type":["array","null"],"minItems":1,"description":"The addresses messages sent with this subject are e-mailed to. Send `null` to use `CONTACT_US_EMAIL_TO` instead; an empty list is rejected with `400`.","items":{"type":"string","format":"email","maxLength":254}}}},"ContactUsSubject":{"type":"object","description":"A contact us subject offered on the storefront contact form.","properties":{"pk":{"type":"integer","readOnly":true,"description":"The unique identifier of the subject."},"text":{"type":"string","maxLength":60,"description":"The subject label, in the request language (falls back to the default language when no translation exists)."},"is_order_needed":{"type":"boolean","description":"Whether the storefront contact form requires an order to be selected for this subject."},"recipients":{"type":["array","null"],"description":"The addresses messages sent with this subject are e-mailed to. When `null`, the storefront uses `CONTACT_US_EMAIL_TO`.","items":{"type":"string","format":"email","maxLength":254}}}},"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"}}}},"ContactUsSubjectNotFound":{"description":"The requested contact us subject does not exist.","content":{"application/json":{"schema":{"$ref":"#/components/schemas/Error"}}}}}},"paths":{"/contact-us-subjects/{id}/":{"patch":{"tags":["Contact Us Subjects"],"operationId":"partialUpdateContactUsSubject","summary":"Partially update a contact us subject","description":"Updates only the fields sent. Outside the default language, `text` is written only as the translation for the request language (see **Translations** and `IGNORE_ACCEPT_LANGUAGE_HEADER` in the section description).","requestBody":{"required":true,"content":{"application/json":{"schema":{"$ref":"#/components/schemas/ContactUsSubjectPatchRequest"}}}},"responses":{"200":{"description":"The updated contact us subject.","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ContactUsSubject"}}}},"400":{"$ref":"#/components/responses/ValidationError"},"401":{"$ref":"#/components/responses/Unauthorized"},"403":{"$ref":"#/components/responses/Forbidden"},"404":{"$ref":"#/components/responses/ContactUsSubjectNotFound"}}}}}}
```


---

# 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/contact-us-subjects/partially-update-a-contact-us-subject.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.
