# Consent notices {% hint style="warning" %} **Note**: Didomi recommends using the Didomi Console to manage consent notices and reserving the API for edge cases that cannot be handled through the Console. {% endhint %} Consent notices can be fully managed via the Didomi API for automating notices creation, updates, or publishing. The Didomi API manages consent notices and their configuration through the following entities: * [Notices](/api-and-platform/widgets/consent-notices/notices.md): A high-level definition of notices (ID, name, etc.) * [Configurations](/api-and-platform/widgets/consent-notices/configurations.md): The detailed configuration and history of notices * [Deployments](/api-and-platform/widgets/consent-notices/deployments.md): An auditable list of deployed notices We also offer [a step-by-step tutorial for creating, configuring, and publishing a consent notice](/api-and-platform/widgets/consent-notices/tutorials/tutorial.md). --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://developers.didomi.io/api-and-platform/widgets/consent-notices.md?ask= ``` The question should be specific, self-contained, and written in natural language. 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.