# Content API

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

```
GET https://docs.guibo.travel/developers/content-api.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.