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

# Developers

- [Overview](https://docs.guibo.travel/developers/overview.md): Sync content from third-party systems to GUIBO via the Content API. Automate booking-specific Trip Links with travel documents via the Releases API.
- [Releases API](https://docs.guibo.travel/developers/releases-api.md): Automate booking-specific Trip Links with personalized travel documents, re-branded for resellers, directly from your booking system.
- [HOW TO create releases for bookings per API](https://docs.guibo.travel/developers/releases-api/how-to-create-releases-for-bookings-per-api.md): Releases allow you to package and deliver trip information directly to your customers. Depending on your workflow and the level of customization required, GUIBO offers two ways to create a release:
- [Release | Create guidebook release](https://docs.guibo.travel/developers/releases-api/release-or-create-guidebook-release.md): This article describes how to publish guidebook by connecting to another software. Software systems communicate with Application-Programming-Intefaces (API).
- [Release | Create on-demand release](https://docs.guibo.travel/developers/releases-api/create-on-demand-release.md): Generate complete guidebook structure and release in a single API call using flexible JSON payload with inline content or library references.
- [Release | Read release details](https://docs.guibo.travel/developers/releases-api/release-or-read-release-details.md): You can fetch the details of the release by the download cod
- [Release | Update release details](https://docs.guibo.travel/developers/releases-api/release-or-update-release-details.md): After creating a guidebook release, you can update attributes of the release.
- [Release | Revoke guidebook release](https://docs.guibo.travel/developers/releases-api/release-or-revoke-guidebook-release.md): This article describes how to cancel a guidebook release through the GUIBO API. Travellers will not be able to download the guidebook with the given download code any more.
- [Release | Add document to release](https://docs.guibo.travel/developers/releases-api/release-or-add-document-to-release.md): When you add PDF documents to a release, they will be offine available in the App and they will be accessible under the private release link for your customer.
- [Release | Update document in release](https://docs.guibo.travel/developers/releases-api/release-or-update-document-in-release.md): Replace PDF document and its description in a release
- [Release | Delete documents in release](https://docs.guibo.travel/developers/releases-api/release-or-delete-documents-in-release.md): Remove all documents that have been added to the release
- [Release | B2B Webhook](https://docs.guibo.travel/developers/releases-api/release-or-b2b-webhook.md): Receive a POST notification with release metadata when a connected B2B partner shares a new release with your account.
- [Content API](https://docs.guibo.travel/developers/content-api.md): Create and update routes, POIs, text pages, and libraries in GUIBO from external systems — mirror your content data without manual maintenance.
- [HOW TO create Guidebooks per API](https://docs.guibo.travel/developers/content-api/how-to-create-guidebooks-per-api.md)
- [HOW TO  synchronize data with your IT systems](https://docs.guibo.travel/developers/content-api/how-to-synchronize-data-with-your-it-systems.md): In case you already have a system that helps you manage Point-Of-Interests, Routes, Travel Information, etc. you can still use the power of GUIBO to improve your operations.
- [Content | 1. Library](https://docs.guibo.travel/developers/content-api/content-or-create-library-or-guidebook.md): Libraries are the central hubs where you manage your POIs, Routes, and Textpages. Any asset stored in a library can be reused across multiple guidebooks—allowing you to update content in one place and
- [Content | 2. Routes](https://docs.guibo.travel/developers/content-api/content-or-create-and-update-routes.md)
- [Content | 3. Point-Of-Interests (POIs)](https://docs.guibo.travel/developers/content-api/content-or-create-and-update-point-of-interests-pois.md): Hotels and other POIs can be imported into GUIBO automatically via API. A common use case is syncing hotels from a booking system to automatically attach booked accommodations to a guest's guidebook.
- [Content | 4. Geodata properties](https://docs.guibo.travel/developers/content-api/content-or-4.-geodata-properties.md): Updating properties for Routes and POIs
- [Content | 5. Text page](https://docs.guibo.travel/developers/content-api/content-or-create-text-page.md)
- [Content | 6. Guidebook](https://docs.guibo.travel/developers/content-api/content-or-create-library-or-guidebook-1.md): Guidebooks contain the complete itinerary for your travel products, giving travelers everything they need to know throughout their journey.
- [Content | 7. Stage](https://docs.guibo.travel/developers/content-api/content-or-create-category.md): 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.
- [Content | 8. Assembling the guidebook](https://docs.guibo.travel/developers/content-api/content-or-8.-assembling-the-guidebook.md): After setting up the guidebook stages, add your library assets—including routes, POIs, and textpages—to complete the itinerary.
- [Dynamic Packaging API](https://docs.guibo.travel/developers/dynamic-packaging-api.md)
- [Dynamic Packaging | Destination Management](https://docs.guibo.travel/developers/dynamic-packaging-api/dynamic-packaging-or-destination-management.md)
- [Dynamic Packaging | Hotel Management](https://docs.guibo.travel/developers/dynamic-packaging-api/dynamic-packaging-or-hotel-management.md)
- [Dynamic Packaging | Route Management](https://docs.guibo.travel/developers/dynamic-packaging-api/dynamic-packaging-or-route-management.md)


---

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