> 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/ingestion/restful-ingestion.md).

# RESTful Ingestion

REST ingestion guide for Umbraco Compose: upserts, deletes, and bulk payloads.

You can integrate Umbraco Compose with applications that control the payload sent to the Ingestion API.

These scenarios are perfect for standard RESTful ingestion.

If you do not have control over the payload sent by your application, then you may wish to consider using an [Ingestion Function](/umbraco-compose/apis/ingestion/functions.md) instead.

## Making an Ingestion Request

The RESTful ingestion endpoint expects an HTTP `PUT` request. The body of the request should be `application/json` and should consist an array of [Ingestion objects](/umbraco-compose/apis/ingestion/ingestion-structure.md).

An example of ingesting a single content item might look like the following:

```http
PUT /{project-alias}/{environment-alias}/{collection-alias}
Host: ingest.{region}.umbracocompose.com
Content-Type: application/json
Authorization: Bearer {access-token}

[
  {
    "id": "1",
    "type": "Software",
    "data": {
      "name": "Umbraco Compose"
    },
    "action": "upsert"
  }
]
```


---

# 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/ingestion/restful-ingestion.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.