> For the complete documentation index, see [llms.txt](https://docs.umbraco.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.umbraco.com/umbraco-cms/develop-with-umbraco/headless-and-apis.md). # Headless & APIs Deliver content to headless frontends, manage Umbraco programmatically, and trigger webhooks from content events. Umbraco provides a set of APIs for consuming and managing content outside the backoffice. Use the Content Delivery API to power headless and decoupled frontends, the Management API to manage content programmatically, and webhooks to notify external systems when content changes.
Content Delivery APIA read-only REST API for delivering Umbraco content to headless and decoupled frontends.Content Delivery API
Management APIA REST API for creating, updating, and managing Umbraco content and configuration programmatically.Management API
WebhooksConfigure webhooks to send HTTP notifications to external systems when content events occur.Webhooks
--- # 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://docs.umbraco.com/umbraco-cms/develop-with-umbraco/headless-and-apis.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.