> For the complete documentation index, see [llms.txt](https://developers.didomi.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developers.didomi.io/api-and-platform/consents/events.md). # Events A consent event is a partial update to the consent status of a user. The `/consents/events` endpoint of the API exposes the events managed by Didomi for your organizations. A full reference of the endpoint and the resources it returns is available [here](https://didomi.stoplight.io/docs/didomi-api/ZG9jOjU2ODQ0NTc-introduction). When an end-user makes consent choices through your own custom UI, your organization should create a new consent event on the Didomi platform. The end-user consent status, for a given regulation, will be automatically updated and the history of consent events will be kept, associated with the end-user. {% hint style="info" %} By default, it applies to GDPR regulation, but it can also be associated with other regulations such as CPRA. [Click here](/api-and-platform/data-manager/regulations.md#regulations-available) to see all regulations supported by Didomi. {% endhint %} *** --- # 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://developers.didomi.io/api-and-platform/consents/events.md?ask=&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.