> 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.md).

# Content API

Create and update routes, POIs, text pages, and libraries in GUIBO from external systems — mirror your content data without manual maintenance.

## Content API

The Content API handles **content data** — the reusable building blocks of your travel products: routes, POIs, text pages, libraries, and guidebooks. This data is static and maintained season to season, not per booking.

#### When to use the Content API

You already manage geo data or text content in a third-party system and want to **mirror it into GUIBO libraries** — so you maintain it in one place only, with no copies that drift out of sync.

For the full integration workflow, see [Data Integration](/content-management/integrate-external-content.md).

#### Endpoints

| Endpoint                                                                                                  | Purpose                                      |
| --------------------------------------------------------------------------------------------------------- | -------------------------------------------- |
| [Create library or guidebook](/developers/content-api/content-or-create-library-or-guidebook-1.md)        | Create the containers that hold your content |
| [Create day/stage](/developers/content-api/content-or-create-category.md)                                 | Add day/stage categories to guidebooks       |
| [Create and update POIs](/developers/content-api/content-or-create-and-update-point-of-interests-pois.md) | Sync hotels, sights, restaurants, services   |
| [Create and update routes](/developers/content-api/content-or-create-and-update-routes.md)                | Sync cycling, hiking, or transfer routes     |
| [Create text page](/developers/content-api/content-or-create-text-page.md)                                | Sync info pages, FAQs, arrival instructions  |

#### How it connects

Content created via this API is used in two ways:

1. **Imported into guidebooks** — manually or dynamically (auto-import POIs near routes)
2. **Referenced in releases** — the Releases API adds booking-specific data on top of this content


---

# 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.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.