> 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-8.-assembling-the-guidebook.md).

# Content | 8. Assembling the guidebook

After setting up the guidebook stages, add your library assets—including routes, POIs, and textpages—to complete the itinerary.

#### **A) Add Route or POI to Stage**

Replace <mark style="color:orange;">GGGGGG</mark> with the guidebook ID

Replace <mark style="color:orange;">CCCCCC</mark> with the category ID where the asset should be placed

You can use either the GUIBO ID (link) to identify the geoasset or the external ID

```bash
curl --location 'https://services.schneidergeo.com/content/guidebook/GGGGGG/import/manual/geoasset' \
--header 'Authorization: xxxx-xxxxx-xxxxx-xxxx' \
--header 'Content-Type: application/json' \
--data '{links: ["3QT3sM"], category: "CCCCCC"}'


curl --location 'https://services.schneidergeo.com/content/guidebook/GGGGGG/import/manual/geoasset' \
--header 'Authorization: xxxx-xxxxx-xxxxx-xxxx' \
--header 'Content-Type: application/json' \
--data '{customIDs: ["ROUTE_1","ROUTE_2"], category: "CCCCCC"}'
```

#### B) Connect library to guidebook

Once a library is linked to a guidebook, GUIBO automatically identifies all POIs located along the guidebook’s routes and assigns them to the appropriate stages.

Any subsequent changes to your routes or POIs—including additions, updates, or deletions—will automatically trigger a real-time sync to update the guidebook's POI selection.

To create a connection, you currently need the internal IDs of guidebook and library

Replace <mark style="color:orange;">GGGGGG</mark> with the guidebook ID

Replace <mark style="color:orange;">LLLLLL</mark> with the library ID

```shellscript
curl --url 'https://services.schneidergeo.com/content/guidebook/GGGGGG/connect/library/LLLLLL' \
  --header 'Content-Type: application/json'  \
  --header 'Authorization: xxxx-xxxxx-xxxxx-xxxx' \

```

#### **C) Add Textpage**

Replace <mark style="color:orange;">GGGGGG</mark> with the guidebook ID

Replace <mark style="color:orange;">CCCCCC</mark> with the category ID where the asset should be placed

You can use either the GUIBO ID (link) to identify the geoasset or the external ID

You can set a category ID to place it in a stage, otherwise it will be placed in "Good To know"

```shellscript
curl --location 'https://services.schneidergeo.com/content/guidebook/GGGGGG/import/manual/text' \
--header 'Authorization: xxxx-xxxxx-xxxxx-xxxx' \
--header 'Content-Type: application/json' \
--data '{links: ["3QT3sM"], category: "CCCCCC"}'


curl --location 'https://services.schneidergeo.com/content/guidebook/GGGGGG/import/manual/text' \
--header 'Authorization: xxxx-xxxxx-xxxxx-xxxx' \
--header 'Content-Type: application/json' \
--data '{customIDs: ["TXT_1","TXT2"], category: "CCCCCC"}'
```


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.guibo.travel/developers/content-api/content-or-8.-assembling-the-guidebook.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.