> 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-compose/apis.md).

# APIs

- [API Overview](https://docs.umbraco.com/umbraco-compose/apis/api-overview.md): Get an overview of the available APIs.
- [Management](https://docs.umbraco.com/umbraco-compose/apis/management.md): The Management API is where you can administrate all non-content aspects of your project.
- [API Applications](https://docs.umbraco.com/umbraco-compose/apis/management/api-applications.md): An API Application is a security identity used for accessing projects and their resources through the Management API.
- [Aliases](https://docs.umbraco.com/umbraco-compose/apis/management/aliases.md): Aliases identify Management API entities. Learn the naming rules, validation constraints, and reserved values that you cannot use.
- [Ingestion](https://docs.umbraco.com/umbraco-compose/apis/ingestion.md): Learn how to authenticate and ingest content into Umbraco Compose using the Ingestion API, including prerequisites, endpoint format, and links to API docs.
- [Ingestion Structure](https://docs.umbraco.com/umbraco-compose/apis/ingestion/ingestion-structure.md): An overview of available operations for modifying ingested content.
- [RESTful Ingestion](https://docs.umbraco.com/umbraco-compose/apis/ingestion/restful-ingestion.md): REST ingestion guide for Umbraco Compose: upserts, deletes, and bulk payloads.
- [Functions](https://docs.umbraco.com/umbraco-compose/apis/ingestion/functions.md): Use ingestion functions to transform webhook payloads into Umbraco Compose’s ingestion format, with examples, creation or invocation steps, and runtime limits.
- [GraphQL](https://docs.umbraco.com/umbraco-compose/apis/graphql.md): Introduces how to access and query content from Umbraco Compose using the GraphQL API.
- [Filtering](https://docs.umbraco.com/umbraco-compose/apis/graphql/filtering.md): Explains how to filter GraphQL query results in Umbraco Compose using field conditions, filter methods, and boolean logic.
- [Pagination](https://docs.umbraco.com/umbraco-compose/apis/graphql/pagination.md): Explains how pagination and query complexity limits work in the Umbraco Compose GraphQL API.
- [Sorting](https://docs.umbraco.com/umbraco-compose/apis/graphql/sorting.md): Explains how to sort GraphQL query results using single, multiple, and nested \`orderBy\` criteria.
- [Persisted Documents](https://docs.umbraco.com/umbraco-compose/apis/graphql/persisted-documents.md): This article explains how to create, manage, and invoke persisted GraphQL documents in Umbraco Compose using aliases for improved performance and maintainability.


---

# 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-compose/apis.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.