> 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/user-field-history.md).

# User Field History

Administrative endpoint for reading **user field change history** — a read-only audit log that records when and why a user's permission fields changed.

### Tracked Fields

| Field              | Description                                                |
| ------------------ | ---------------------------------------------------------- |
| `email_allowed`    | Whether the user has opted in to email communication.      |
| `sms_allowed`      | Whether the user has opted in to SMS communication.        |
| `call_allowed`     | Whether the user has opted in to phone call communication. |
| `whatsapp_allowed` | Whether the user has opted in to WhatsApp communication.   |

### Change Sources

| Source  | Description                                                     |
| ------- | --------------------------------------------------------------- |
| `user`  | Changed by the user through the storefront profile page.        |
| `iys`   | Updated by the IYS subscription webhook.                        |
| `crm`   | Updated by a CRM integration.                                   |
| `kvkk`  | Updated by the KVKK consent gateway or unsubscription endpoint. |
| `admin` | Updated through the admin API.                                  |
| `hook`  | Updated by a generic subscription service webhook.              |

### Filtering & Ordering

Filter by `user_id`, `field_name`, or `source`. Results are ordered by `created_date` descending by default; pass `?sort=created_date` to reverse.


---

# 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/user-field-history.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.
