> 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-heartcore/api-documentation/content-delivery.md). # Content Delivery Documentation for Heartcore Content Delivery APIs This is the read-only API for delivering published content and media to any app, website, device or platform. It’s worth noting that the JSON output for both Content and Media vary depending on how a given ContentType or MediaType is defined. ## Cultures Specific to Content in the Content Delivery API. To request content in a specific language, a culture parameter can be specified. When no culture is specified its treated as invariant and the default language will be returned. ### Access via an Accept-Language header ```http GET https://cdn.umbraco.io/content Accept-Language: en-US ``` ### Acces via a Query String parameter ```http GET https://cdn.umbraco.io/content?culture=en-US ``` ## [Content endpoints](/umbraco-heartcore/api-documentation/content-delivery/content.md) Content endpoints for retrieving specific content by ID or URL. It is also possible to retrieve children, descendants and ancestors structured according to the Content tree structure. ## [Media endpoints](/umbraco-heartcore/api-documentation/content-delivery/media.md) Media endpoints for retrieving specific media by id. It is also possible getting children of a media folder structured according to the Media tree structure. --- # 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-heartcore/api-documentation/content-delivery.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.