> 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/publishing/how-to-publish/how-to-publish.md).

# Releases

## What is a release?

A **release** is the booking-specific unit of publishing in GUIBO: every booking gets its own release, and this page explains what it contains and which settings control traveler access.

### Release components

<table><thead><tr><th width="219.28515625">Component</th><th>Contents</th></tr></thead><tbody><tr><td><strong>Guidebook</strong></td><td>The full itinerary data — every part of it can be customized per booking.</td></tr><tr><td><strong>Accommodation bookings</strong></td><td>The booked accommodations with arrival date, departure date, and booking-specific comments.</td></tr><tr><td><strong>PDF attachments</strong></td><td>Booking-related PDF documents (e.g. vouchers, tickets) delivered to travelers via the Trip Link and in the Tour Guide App.</td></tr><tr><td><strong>Metadata</strong></td><td>All settings that control access — see below.</td></tr></tbody></table>

### Release creation types

#### Template-based releases

The release is created from a pre-existing guidebook in GUIBO. Booking-specific data is added during release creation: **accommodation bookings**, **PDF attachments**, and any other guidebook customization.

Create template-based releases via:

* **Web portal** — manually, by users
* **API** — automated, typically triggered from a booking system

#### On-demand releases

The release is created without a pre-existing guidebook — the guidebook is defined dynamically as part of the release creation. Source content can be provided from external systems or from GUIBO libraries.

On-demand releases are created via **API only**.

#### Which create type fits my setup?

Choose **template-based** when all bookings of a product share the same itinerary — the guidebook serves as the template, and only accommodations and documents vary per booking.

Choose **on-demand** when the itinerary differs from booking to booking, e.g. tailor-made trips assembled in an external trip builder. See Integrate External Content for a full comparison.

### Release metadata

<table><thead><tr><th width="199.4765625">Field</th><th>Description</th></tr></thead><tbody><tr><td><code>ID</code></td><td>Unique ID of the release</td></tr><tr><td><code>Guidebook</code></td><td>Name of the guidebook attached to this release</td></tr><tr><td><code>Operator</code></td><td>GUIBO account operating this booking</td></tr><tr><td><code>Operator Code</code></td><td>Traveler download code for the operator — typically the operator's booking number</td></tr><tr><td><code>Seller</code></td><td>GUIBO account selling this booking</td></tr><tr><td><code>Seller Code</code></td><td>Traveler download code for the seller — typically the seller's booking number</td></tr><tr><td><code>Download period</code></td><td>Time window during which the traveler has access to the guidebook</td></tr><tr><td><code>Max devices</code></td><td>Maximum number of devices that can download the guidebook via the Tour Guide App — typically the number of travelers</td></tr><tr><td><code>Language</code></td><td>Language of the release</td></tr><tr><td><code>Status</code></td><td>Status of the release. A release is downloadable only while status is <strong>active</strong>.</td></tr><tr><td><code>Publishing App</code></td><td>Traveler download option for the Tour Guide App</td></tr><tr><td><code>Publishing PDF</code></td><td>Traveler download option for the Roadbook PDF via Trip Link</td></tr><tr><td><code>Publishing GPX</code></td><td>Traveler download option for GPX files via Trip Link</td></tr><tr><td><code>Trip Link</code></td><td>The traveler's link to access all booking-related trip information</td></tr></tbody></table>

## Next step

Continue with [Create a release](/publishing/how-to-publish/create-releases.md) to see how releases are created — manually or automated per booking.

A **release** is the booking-specific unit of publishing in GUIBO: every booking gets its own release, and this page explains what it contains and how it is created.

## What a release consists of

<table><thead><tr><th width="196.09765625">Component</th><th>Contents</th></tr></thead><tbody><tr><td><strong>Guidebook</strong></td><td>The full itinerary data — every part of it can be customized per booking.</td></tr><tr><td><strong>Accommodation bookings</strong></td><td>The booked accommodations with arrival date, departure date, and booking-specific comments.</td></tr><tr><td><strong>PDF attachments</strong></td><td>Booking-related PDF documents (e.g. vouchers, tickets) delivered to travelers via the Trip Link and in the Tour Guide App.</td></tr><tr><td><strong>Metadata</strong></td><td>All settings that control access — see <a href="#release-metadata">here</a>.</td></tr></tbody></table>

## How releases are created

### Template-based releases

The release is created from a pre-existing guidebook. Booking-specific data is added during release creation: **accommodation bookings**, **PDF attachments**, and any other guidebook customization.

Create template-based releases via:

* **Web portal** — manually, by users
* **API** — automated, typically triggered from a booking system

### On-demand releases

The release is created without a pre-existing guidebook — the guidebook is defined dynamically as part of the release creation. Source content can come from external systems or from GUIBO libraries.

On-demand releases are created via **API only**.

### Which creation method fits my setup?

Choose **template-based** when all bookings of a product share the same itinerary — the guidebook serves as the template, and only accommodations and documents vary per booking.

Choose **on-demand** when the itinerary differs from booking to booking, e.g. tailor-made trips assembled in an external trip builder. See Integrate External Content for a full comparison.

### Related pages

* How to publish — publishing channels and methods
* Trip Link — the traveler's central access point
* Releases API — automate release creation

A **release** is a traveler-specific instance of your guidebook that:

* Represents a single booking
* Contains personalized information for specific travelers
* Provides access through multiple delivery channels
* Is active during a defined time period
* Is accessed via unique download codes

### Publishing Channels

Each release automatically generates content across multiple channels:

<table><thead><tr><th>Channel</th><th width="399.35626220703125">Description</th><th>Availability</th></tr></thead><tbody><tr><td><strong>Trip Link</strong></td><td>Central access point with unique web link for this release</td><td>Always included</td></tr><tr><td><strong>Tour Guide App</strong></td><td>Mobile app with offline maps, navigation, and real-time updates</td><td>Always included</td></tr><tr><td><strong>Roadbook PDF</strong></td><td>Print-ready travel document with maps and itinerary details</td><td>Optional</td></tr><tr><td><strong>B2B Network</strong></td><td>Share releases with resellers so they can forward a re-branded Trip Link to the traveler</td><td>Optional</td></tr><tr><td><strong>TourMaps</strong></td><td>Interactive maps for webshop integration (guidebook-level, not booking-specific)</td><td>Always available</td></tr></tbody></table>

### Publishing Methods

#### Manual Publishing

Create releases individually through the GUIBO web portal:

1. Navigate to **Release Dashboard**
2. Click the orange **+** button
3. Enter booking details
4. Optionally add personalized content
5. Share the Trip Link with travelers

**Best for:** Small operations, testing, or individual bookings

#### API Publishing

Automate release creation from your booking system:

* **100% automated** publishing process
* **Real-time** release generation
* **Personalized** content per booking
* **Scalable** for high booking volumes

**Best for:** Integration with booking systems, high-volume operations

Learn more: [Releases API](/developers/releases-api.md)

### Release Types

#### Guidebook-based Releases

Create releases from existing guidebooks:

* **Guidebook** serves as product template
* **Updated seasonally** in GUIBO
* **Personalized per booking** (accommodations, documents, dates)
* **Same structure** for all bookings of this product

**Best for:** Standardized tours with consistent itineraries

Learn more: [Release | Create guidebook release](/developers/releases-api/release-or-create-guidebook-release.md) (via API)

#### On-demand Releases

Generate complete guidebook and release simultaneously via API:

* **Fully dynamic** guidebook structure
* **Created per booking** from JSON payload
* **No pre-existing** guidebook required
* **Maximum flexibility** for unique itineraries

**Best for:** Tailor-made trips, highly variable tours, third-party system integration

Learn more: [Create on-demand release](/developers/releases-api/release-or-create-guidebook-release/create-on-demand-release.md)

### Personalization Options

All releases support booking-specific customization:

* **Accommodations** with arrival/departure dates and comments
* **Additional documents** (vouchers, tickets, confirmations)
* **Custom content** (POIs, routes, text pages)
* **Modified content** from the base guidebook

Learn more: [Personalized Accommodation](broken://pages/dCpXCx6xVKUTP5vue8ZG), [Release | Create guidebook release](/developers/releases-api/release-or-create-guidebook-release.md) (via API)

### Canceling a Release

A Release cannot be deleted. However, you can cancel a release in the release dashboard by changing the status from ACTIVE to CANCELED, provided that the download period has not yet started. Please note that the code will remain blocked and cannot be reassigned.


---

# 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/publishing/how-to-publish/how-to-publish.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.