> 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/how-to-create-guidebooks-per-api.md).

# HOW TO create Guidebooks per API

**Prerequisites**

We recommend completing these initial setup steps manually in the GUI, as they only need to be performed once:

1. Create a POI Library: Set up at least one library dedicated to POIs. ([manually](/get-started/getting-started.md#prepare-library) / [API](/developers/content-api/content-or-create-library-or-guidebook.md#a-create-geodata-library))
2. Create a Route Library: Set up at least one library dedicated to Routes. ([manually](/get-started/getting-started.md#prepare-library) / [API](/developers/content-api/content-or-create-library-or-guidebook.md#a-create-geodata-library))
3. Set the Default Accommodation Library: Create a Geodata library, then navigate to Account Settings to set it as your default accommodation library.
4. Set the Default Destination Library: Create a Geodata library, dedicated for destinations only

### Recommended Workflow: Automated Guidebook Creation via API

**Follow this sequence to fully automate your guidebook creation process:**

1. Populate Libraries *(Perform as needed)*
   * [Add POIs to your POI library](/developers/content-api/content-or-create-and-update-point-of-interests-pois.md).&#x20;
   * [Add Routes to your Route library.](/developers/content-api/content-or-create-and-update-routes.md)
   * Add hotels to your accommodation library using the same process as adding POIs.
2. Structure the Guidebook
   * [Create the Guidebook.](/developers/content-api/content-or-create-library-or-guidebook-1.md#a-create-guidebook)
   * [Create the Stages within the Guidebook.](/developers/content-api/content-or-create-category.md)
3. Assemble the Content
   * [Add Routes to their respective Stages.](/developers/content-api/content-or-8.-assembling-the-guidebook.md)
   * Add POIs to Stages using one of two methods:
     * Option A: [Programmatically add each POI individually](/developers/content-api/content-or-8.-assembling-the-guidebook.md#a-add-route-or-poi-to-stage).
     * Option B: [Link the library directly to the Guidebook](/developers/content-api/content-or-8.-assembling-the-guidebook.md#b-connect-library-to-guidebook)—GUIBO will automatically match and attach all POIs along the routes.
   * [Add Textpages to complete the itinerary.](/developers/content-api/content-or-8.-assembling-the-guidebook.md#c-add-textpage)


---

# 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/how-to-create-guidebooks-per-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.
