> For the complete documentation index, see [llms.txt](https://docs.guibo.travel/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.guibo.travel/developers/content-api/content-or-create-category.md).

# Content | 7. Stage

Stages form the top-level structure of your guidebooks. Set up a stage for the arrival day as well as each distinct segment or day of the trip.

There are two ways to create a stage and assign it to a guidebook. A stage can only exist inside a guidebook.

Assign to guidebook with

**a)** The GUIBO Guidebook Link inside the request body in attribute "bundle" or

**b)** The custom ID of the guidebook  as request parameter, together with the account ID . You can then leave the guidebook ID in the request body empty.

* You can find the Account ID under Account Settings > General Settings > Account ID
* You can find the API key under Account Settings > General Settings > API Key

## Body

```json
curl --location -X POST 'https://services.schneidergeo.com/content/category' \
--header 'Authorization: xxxx-xxxxxx-xxxxx-xxxxxx' \
--header 'Content-Type: application/json' \
--data '{   
    "bundle":"XUwfwA",
    "names": {
        "de":"Day 14",
        "en":"Day 14"
    },
    "sorting":2

}'
```

#### Query Parameters

| Name           | Type   | Description |
| -------------- | ------ | ----------- |
| bundleCustomId | String |             |

#### Headers

| Name                                            | Type   | Description |
| ----------------------------------------------- | ------ | ----------- |
| Authorization<mark style="color:red;">\*</mark> | String | API key     |


---

# 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.guibo.travel/developers/content-api/content-or-create-category.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.